Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760044b1a3c8fd00411072429684462d214e05a5159a89a59d9b510c90a80471

Tx prefix hash: 9c1f0b31ae151a31d1d9095f76213195cfbd08fb6adfd16f86db8b9b4a7a87fc
Tx public key: 557caf3e2647c9ec85e4b3f68c2379eb091001dd96ffce3e3553c474031b4084
Timestamp: 1723321884 Timestamp [UCT]: 2024-08-10 20:31:24 Age [y:d:h:m:s]: 00:240:07:00:15
Block: 1085098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171606 RingCT/type: yes/0
Extra: 01557caf3e2647c9ec85e4b3f68c2379eb091001dd96ffce3e3553c474031b4084021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7af929801344c58749f9fcc57b282a26cc0d7aec6e86682b26d0ac7b9d0acb20 0.600000000000 1559599 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": 1085108, "vin": [ { "gen": { "height": 1085098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af929801344c58749f9fcc57b282a26cc0d7aec6e86682b26d0ac7b9d0acb20" } } ], "extra": [ 1, 85, 124, 175, 62, 38, 71, 201, 236, 133, 228, 179, 246, 140, 35, 121, 235, 9, 16, 1, 221, 150, 255, 206, 62, 53, 83, 196, 116, 3, 27, 64, 132, 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