Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc0817ba9ba274dd477acdf3c110db3dae1f387a1899864b04f2e91d9684d1f

Tx prefix hash: 88523d53b4332e4532deea8f8971e14dfe6f504923bb797b0af1fa275e3ad28d
Tx public key: 0142f195ac956f2f0e0020a5b766463914caae394dea4dc3f719fe0bd59367cf
Timestamp: 1704603806 Timestamp [UCT]: 2024-01-07 05:03:26 Age [y:d:h:m:s]: 01:017:10:20:33
Block: 929895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273761 RingCT/type: yes/0
Extra: 010142f195ac956f2f0e0020a5b766463914caae394dea4dc3f719fe0bd59367cf02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07f6fe9712dd436fef83340e12b5eefba53e9947bc67cfdc11dc602d1f9b2469 0.600000000000 1387771 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": 929905, "vin": [ { "gen": { "height": 929895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07f6fe9712dd436fef83340e12b5eefba53e9947bc67cfdc11dc602d1f9b2469" } } ], "extra": [ 1, 1, 66, 241, 149, 172, 149, 111, 47, 14, 0, 32, 165, 183, 102, 70, 57, 20, 202, 174, 57, 77, 234, 77, 195, 247, 25, 254, 11, 213, 147, 103, 207, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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