Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9f19b8fa7be686865cd150f4530de0ba352dfc3c25823cd9f71bf051a7daf0ca

Tx prefix hash: 3286d2aa7bf1f1a89ccfd4d42880f768a9d7ce51f87daa29c4aba74fd62b1793
Tx public key: a153f6e002132d805ab482ffe6ce6a8d12d76ebc02cccba7d5888fb181f117aa
Timestamp: 1761544569 Timestamp [UCT]: 2025-10-27 05:56:09 Age [y:d:h:m:s]: 00:067:14:48:45
Block: 1398872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48407 RingCT/type: yes/0
Extra: 01a153f6e002132d805ab482ffe6ce6a8d12d76ebc02cccba7d5888fb181f117aa0211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1484f295635dce26a526dbd81b8be90fdb7616fbc107a30fdfdaf4bfbbc518e4 0.600000000000 1887173 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1398882, "vin": [ { "gen": { "height": 1398872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1484f295635dce26a526dbd81b8be90fdb7616fbc107a30fdfdaf4bfbbc518e4" } } ], "extra": [ 1, 161, 83, 246, 224, 2, 19, 45, 128, 90, 180, 130, 255, 230, 206, 106, 141, 18, 215, 110, 188, 2, 204, 203, 167, 213, 136, 143, 177, 129, 241, 23, 170, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8