Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97ff88aa05e7eac0ebc4f2546b685bddc95fbed3daac7f10a8cc68f3eca5a8b

Tx prefix hash: 79a7c8e9867ef01055bf397b1b7445bd25ff9b9c09fe0cd5221438f9f6a38471
Tx public key: 248a0e547c1327c7343ebb377f0f76fb44bcd0fe8da07bb3ec28cb7300f6ee67
Timestamp: 1681682054 Timestamp [UCT]: 2023-04-16 21:54:14 Age [y:d:h:m:s]: 01:364:11:13:05
Block: 740116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521775 RingCT/type: yes/0
Extra: 01248a0e547c1327c7343ebb377f0f76fb44bcd0fe8da07bb3ec28cb7300f6ee670211000000055029cbac000000000000000000

1 output(s) for total of 2.166150727000 dcy

stealth address amount amount idx
00: 9268b8fdc9d260f42b280a83e1a3bb069073d7249c89a9bec32fb7ee34f3ca23 2.166150727000 1186997 of 0

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": 740126, "vin": [ { "gen": { "height": 740116 } } ], "vout": [ { "amount": 2166150727, "target": { "key": "9268b8fdc9d260f42b280a83e1a3bb069073d7249c89a9bec32fb7ee34f3ca23" } } ], "extra": [ 1, 36, 138, 14, 84, 124, 19, 39, 199, 52, 62, 187, 55, 127, 15, 118, 251, 68, 188, 208, 254, 141, 160, 123, 179, 236, 40, 203, 115, 0, 246, 238, 103, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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