Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75fa365394a410f5120f11b0bc7a82bce86801b780a62aad5630df82bbbb095

Tx prefix hash: 25c86bdd78ffd876d1624c92d28f7c57ce5a0d235d6f6c0a3a7c486f2b8fe48a
Tx public key: bb731fb94ae9745552e791eecfb5a949e0bffb16535713cffef6dcce91c4ed93
Timestamp: 1681480720 Timestamp [UCT]: 2023-04-14 13:58:40 Age [y:d:h:m:s]: 01:272:00:57:23
Block: 738454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455924 RingCT/type: yes/0
Extra: 01bb731fb94ae9745552e791eecfb5a949e0bffb16535713cffef6dcce91c4ed93021100000005b3164c24000000000000000000

1 output(s) for total of 2.193792620000 dcy

stealth address amount amount idx
00: 1fe288285a26ce7c38707b411aa18017b2bd7490699ed91741ca3f62b0ce8aa0 2.193792620000 1185141 of 0

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": 738464, "vin": [ { "gen": { "height": 738454 } } ], "vout": [ { "amount": 2193792620, "target": { "key": "1fe288285a26ce7c38707b411aa18017b2bd7490699ed91741ca3f62b0ce8aa0" } } ], "extra": [ 1, 187, 115, 31, 185, 74, 233, 116, 85, 82, 231, 145, 238, 207, 181, 169, 73, 224, 191, 251, 22, 83, 87, 19, 207, 254, 246, 220, 206, 145, 196, 237, 147, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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