Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 754ab308b5992cb7394873b7270bbae2693ab8604d63011178991691f85c9adc

Tx prefix hash: 2ea0e80eb0901d1ca5f4f9819ec7fcba8a0bff23e4f392a916dac2f41edc74d9
Tx public key: 012dc501aad149284a32b7fd97794a5f322b2d3397349f726d043de68e59573b
Timestamp: 1733362602 Timestamp [UCT]: 2024-12-05 01:36:42 Age [y:d:h:m:s]: 00:332:22:44:00
Block: 1168241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235459 RingCT/type: yes/0
Extra: 01012dc501aad149284a32b7fd97794a5f322b2d3397349f726d043de68e59573b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17a14cd001006eddabf63392ca68df6d6f4c8306e44f6deb7f23f7df3d62e69 0.600000000000 1653948 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": 1168251, "vin": [ { "gen": { "height": 1168241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17a14cd001006eddabf63392ca68df6d6f4c8306e44f6deb7f23f7df3d62e69" } } ], "extra": [ 1, 1, 45, 197, 1, 170, 209, 73, 40, 74, 50, 183, 253, 151, 121, 74, 95, 50, 43, 45, 51, 151, 52, 159, 114, 109, 4, 61, 230, 142, 89, 87, 59, 2, 17, 0, 0, 0, 4, 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