Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97137c1d5a82062823dd3624b0d343e87f23f553f98d0101e4ba208e30326a0

Tx prefix hash: e9717be49144e0220f4b433991a0acf8e0e4a99a33f735303309210e19b68e76
Tx public key: b968e67cb635caf41472636fb53584f1f89e5fd34f28d201d93279f5f36fe906
Timestamp: 1715146710 Timestamp [UCT]: 2024-05-08 05:38:30 Age [y:d:h:m:s]: 01:008:08:07:01
Block: 1017327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266877 RingCT/type: yes/0
Extra: 01b968e67cb635caf41472636fb53584f1f89e5fd34f28d201d93279f5f36fe90602110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee0c2f1ea0fec5dddab1cd869f37a4d51f4174c71df59240569ab14c1f7455fe 0.600000000000 1481100 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": 1017337, "vin": [ { "gen": { "height": 1017327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee0c2f1ea0fec5dddab1cd869f37a4d51f4174c71df59240569ab14c1f7455fe" } } ], "extra": [ 1, 185, 104, 230, 124, 182, 53, 202, 244, 20, 114, 99, 111, 181, 53, 132, 241, 248, 158, 95, 211, 79, 40, 210, 1, 217, 50, 121, 245, 243, 111, 233, 6, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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