Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8073963c1f3f23c5fa5bed0d502b3ae402e2c4a70c7971443682c4b7202ef276

Tx prefix hash: d51645ca93ed314284cb7fee2a3e4b3974e2f13d1b9ec1eee620f64fd34e950a
Tx public key: 4a801a9bbea23af780fbc69234181a450ecee414ddd7c7ac80cfc3d406d2332c
Timestamp: 1696130616 Timestamp [UCT]: 2023-10-01 03:23:36 Age [y:d:h:m:s]: 01:236:02:59:51
Block: 859869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429854 RingCT/type: yes/0
Extra: 014a801a9bbea23af780fbc69234181a450ecee414ddd7c7ac80cfc3d406d2332c0211000000084b8f5122000000000000000000

1 output(s) for total of 0.868754559000 dcy

stealth address amount amount idx
00: a223d321c5d3c272431715fd218bb5f1942f3a54e0e4f2054e2cbeca4f69824f 0.868754559000 1314119 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": 859879, "vin": [ { "gen": { "height": 859869 } } ], "vout": [ { "amount": 868754559, "target": { "key": "a223d321c5d3c272431715fd218bb5f1942f3a54e0e4f2054e2cbeca4f69824f" } } ], "extra": [ 1, 74, 128, 26, 155, 190, 162, 58, 247, 128, 251, 198, 146, 52, 24, 26, 69, 14, 206, 228, 20, 221, 215, 199, 172, 128, 207, 195, 212, 6, 210, 51, 44, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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