Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb27702f0fbd9e423836285e441b9813d0d49dc4c4d634cde573860c8e075bf

Tx prefix hash: 2993150053b8a96ace197b490482b0e5f49843515077e4a6007a97df2310788f
Tx public key: cf89628e4e11a80ac7d576cef148061ed9521ccd6f176e75f427c8171d1dc07e
Timestamp: 1746053992 Timestamp [UCT]: 2025-04-30 22:59:52 Age [y:d:h:m:s]: 00:204:10:39:51
Block: 1273031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143829 RingCT/type: yes/0
Extra: 01cf89628e4e11a80ac7d576cef148061ed9521ccd6f176e75f427c8171d1dc07e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 101b6147dda184d8f954df476fd996e6b5b129b59d06309d7f025998f39321e7 0.600000000000 1760308 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": 1273041, "vin": [ { "gen": { "height": 1273031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "101b6147dda184d8f954df476fd996e6b5b129b59d06309d7f025998f39321e7" } } ], "extra": [ 1, 207, 137, 98, 142, 78, 17, 168, 10, 199, 213, 118, 206, 241, 72, 6, 30, 217, 82, 28, 205, 111, 23, 110, 117, 244, 39, 200, 23, 29, 29, 192, 126, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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