Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4cd162c4bcf890e5641245a5e0dd35b811836a0efe96d109f1304ebb79f2949

Tx prefix hash: c0b6c1219aa8eed69f7f86d6264721134eaee4dfc00ef1602867ae3a767b6c6c
Tx public key: c7c2fde0fd6190b94f27cb330c857bdf3479ca9aba478de1b899e5c4bb6bd00f
Timestamp: 1733942329 Timestamp [UCT]: 2024-12-11 18:38:49 Age [y:d:h:m:s]: 00:096:13:12:07
Block: 1173061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68771 RingCT/type: yes/0
Extra: 01c7c2fde0fd6190b94f27cb330c857bdf3479ca9aba478de1b899e5c4bb6bd00f02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75d6743a8d0fa081f8a16252899ecc47ac0bb332b7941bd536c94898d20bdd6c 0.600000000000 1659038 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": 1173071, "vin": [ { "gen": { "height": 1173061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75d6743a8d0fa081f8a16252899ecc47ac0bb332b7941bd536c94898d20bdd6c" } } ], "extra": [ 1, 199, 194, 253, 224, 253, 97, 144, 185, 79, 39, 203, 51, 12, 133, 123, 223, 52, 121, 202, 154, 186, 71, 141, 225, 184, 153, 229, 196, 187, 107, 208, 15, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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