Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a10dc9b738c392b3174fdaac864b2f3ab3e0401b3b803c048488922895b40f6

Tx prefix hash: b6790df9adc417956de66a85763e7064bc325a36541e4afe7dfc51aa51fc8973
Tx public key: 0d856c5e99adc5ac36ff7059958f97f7b8edda875b70de47dd2b9e8fa18ba797
Timestamp: 1738952392 Timestamp [UCT]: 2025-02-07 18:19:52 Age [y:d:h:m:s]: 00:285:13:41:37
Block: 1214254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201852 RingCT/type: yes/0
Extra: 010d856c5e99adc5ac36ff7059958f97f7b8edda875b70de47dd2b9e8fa18ba797021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb9523a09f9365cb6b8869a349f33a2e1a698b229dcb261c93f830ee4179a3b 0.600000000000 1701041 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": 1214264, "vin": [ { "gen": { "height": 1214254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb9523a09f9365cb6b8869a349f33a2e1a698b229dcb261c93f830ee4179a3b" } } ], "extra": [ 1, 13, 133, 108, 94, 153, 173, 197, 172, 54, 255, 112, 89, 149, 143, 151, 247, 184, 237, 218, 135, 91, 112, 222, 71, 221, 43, 158, 143, 161, 139, 167, 151, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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