Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0693baa09008c1b455e2f6bddc65b4cc211a103b6de1c4851e563d677beb717

Tx prefix hash: 98cd9681076f9d7ac4461f8862a495972a6b49333dd7bbee16341a96c0c2bc6f
Tx public key: 4539e0f8dc70fbf8c49942f1e8a53d3edfba4c4007f36d9f4c2a2a3221c37b5d
Timestamp: 1707691154 Timestamp [UCT]: 2024-02-11 22:39:14 Age [y:d:h:m:s]: 00:249:15:48:09
Block: 955496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178846 RingCT/type: yes/0
Extra: 014539e0f8dc70fbf8c49942f1e8a53d3edfba4c4007f36d9f4c2a2a3221c37b5d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36ffa668f5b97a36a41d1f5722848f7f55aa8b031d60d97b207c54214a285e7 0.600000000000 1414786 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": 955506, "vin": [ { "gen": { "height": 955496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36ffa668f5b97a36a41d1f5722848f7f55aa8b031d60d97b207c54214a285e7" } } ], "extra": [ 1, 69, 57, 224, 248, 220, 112, 251, 248, 196, 153, 66, 241, 232, 165, 61, 62, 223, 186, 76, 64, 7, 243, 109, 159, 76, 42, 42, 50, 33, 195, 123, 93, 2, 17, 0, 0, 0, 4, 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