Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d297144fe9140a451f70679b9d2803d6452be498a6b065437cff4522a6455b0

Tx prefix hash: 1ec2f01db2ebc5a5af131ea92e0694473e15167aab5e13e3bc7c01a656d6b40a
Tx public key: 6b305ea4e4a15cb9962931cca06532dcaae31a7296af9c4627e208f7efdf2c48
Timestamp: 1735965824 Timestamp [UCT]: 2025-01-04 04:43:44 Age [y:d:h:m:s]: 00:086:17:39:29
Block: 1189792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61761 RingCT/type: yes/0
Extra: 016b305ea4e4a15cb9962931cca06532dcaae31a7296af9c4627e208f7efdf2c480211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1da2f9b4dff7e75e03f7312e42eb9869cbe969090eb5c928ba7306834f23a5 0.600000000000 1676303 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": 1189802, "vin": [ { "gen": { "height": 1189792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1da2f9b4dff7e75e03f7312e42eb9869cbe969090eb5c928ba7306834f23a5" } } ], "extra": [ 1, 107, 48, 94, 164, 228, 161, 92, 185, 150, 41, 49, 204, 160, 101, 50, 220, 170, 227, 26, 114, 150, 175, 156, 70, 39, 226, 8, 247, 239, 223, 44, 72, 2, 17, 0, 0, 0, 1, 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