Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde84af5956a9eeb98611429c5bd3ac8519bf50cb8c58193b0879aa8663c7fd7

Tx prefix hash: f36a018c9cca0a3ca7986d3fa4dafb039b913ee5663e843cb43967f5015c6209
Tx public key: 7a8180e80aeb1f02089b8d037b191d3e76c764ddf28a7ef02bce99e915f415d3
Timestamp: 1730345450 Timestamp [UCT]: 2024-10-31 03:30:50 Age [y:d:h:m:s]: 00:000:11:59:55
Block: 1143237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366 RingCT/type: yes/0
Extra: 017a8180e80aeb1f02089b8d037b191d3e76c764ddf28a7ef02bce99e915f415d30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6653bfb779523862406bf655f32965e2164c4ea880f68e81120cd813a5e368ed 0.600000000000 1627100 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": 1143247, "vin": [ { "gen": { "height": 1143237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6653bfb779523862406bf655f32965e2164c4ea880f68e81120cd813a5e368ed" } } ], "extra": [ 1, 122, 129, 128, 232, 10, 235, 31, 2, 8, 155, 141, 3, 123, 25, 29, 62, 118, 199, 100, 221, 242, 138, 126, 240, 43, 206, 153, 233, 21, 244, 21, 211, 2, 17, 0, 0, 0, 2, 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