Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539031105d97a8692325868728c2400c0aef4c881bf2b82a4c2e5f6909a538a5

Tx prefix hash: 4c5478245e5920e4c726bba5f7e1214a7c9defc7215c1bf27825bbec12a83008
Tx public key: 7be72cb9b19bf822296204d906c68a501a3b11d1632eddd6bac5b6c0acfecc72
Timestamp: 1754597963 Timestamp [UCT]: 2025-08-07 20:19:23 Age [y:d:h:m:s]: 00:058:04:31:56
Block: 1342340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40613 RingCT/type: yes/0
Extra: 017be72cb9b19bf822296204d906c68a501a3b11d1632eddd6bac5b6c0acfecc72021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e83bf0c70d508a04aeaae36e6be994847bb80409c64a6cc8f94d4670d313e80 0.600000000000 1830171 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": 1342350, "vin": [ { "gen": { "height": 1342340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e83bf0c70d508a04aeaae36e6be994847bb80409c64a6cc8f94d4670d313e80" } } ], "extra": [ 1, 123, 231, 44, 185, 177, 155, 248, 34, 41, 98, 4, 217, 6, 198, 138, 80, 26, 59, 17, 209, 99, 46, 221, 214, 186, 197, 182, 192, 172, 254, 204, 114, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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