Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f062c62007fcc3ebc2c7976e4b3d44df12f1441752336cc0193f6db2846c39e

Tx prefix hash: fabe70fb9f04f0d10c16cf5f4a95eaa00aa214719b5153ebc58c505e0a02b291
Tx public key: 691fe1d8649aa91646713177fd910a3c75f54f773f538d436bcfa134c5791109
Timestamp: 1734353098 Timestamp [UCT]: 2024-12-16 12:44:58 Age [y:d:h:m:s]: 00:102:05:36:35
Block: 1176457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72837 RingCT/type: yes/0
Extra: 01691fe1d8649aa91646713177fd910a3c75f54f773f538d436bcfa134c5791109021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2979cfb1ed1fafae2eb3ceaf40e51bc2d1ae17553b8016a9c1f97f513098b818 0.600000000000 1662790 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": 1176467, "vin": [ { "gen": { "height": 1176457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2979cfb1ed1fafae2eb3ceaf40e51bc2d1ae17553b8016a9c1f97f513098b818" } } ], "extra": [ 1, 105, 31, 225, 216, 100, 154, 169, 22, 70, 113, 49, 119, 253, 145, 10, 60, 117, 245, 79, 119, 63, 83, 141, 67, 107, 207, 161, 52, 197, 121, 17, 9, 2, 17, 0, 0, 0, 3, 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