Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18cbd850b19a7b289e200ac40c149241adeb285fc2ddd7cdfd8b31320193ea9d

Tx prefix hash: 1dbc64835c51c761355639ea7e36921dfa50599274d74e2a5d7cebcc08f610ec
Tx public key: 3ddcb0dc9f50621e0643e1fc42be71bebf95cb34e32aa73f89843bd82d4bd2d0
Timestamp: 1726866664 Timestamp [UCT]: 2024-09-20 21:11:04 Age [y:d:h:m:s]: 00:260:02:40:56
Block: 1114484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185765 RingCT/type: yes/0
Extra: 013ddcb0dc9f50621e0643e1fc42be71bebf95cb34e32aa73f89843bd82d4bd2d0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b31820d659b52daa7a531119d9971fb3ceca062dc200e98295b624e349916660 0.600000000000 1594285 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": 1114494, "vin": [ { "gen": { "height": 1114484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b31820d659b52daa7a531119d9971fb3ceca062dc200e98295b624e349916660" } } ], "extra": [ 1, 61, 220, 176, 220, 159, 80, 98, 30, 6, 67, 225, 252, 66, 190, 113, 190, 191, 149, 203, 52, 227, 42, 167, 63, 137, 132, 59, 216, 45, 75, 210, 208, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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