Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e991764c7c6006fd6cab2e673624041eca38687e8230c3a69751f456957d8000

Tx prefix hash: 0b9d04ac960c767f4c16d297f1fad1777f248c5b7347c851062ef9d03d47c385
Tx public key: 8c5d6ad2e8739009e4d3c347396299dde0e544aa064ef3e30fae4a84763a4bcd
Timestamp: 1609830893 Timestamp [UCT]: 2021-01-05 07:14:53 Age [y:d:h:m:s]: 04:058:17:32:57
Block: 174634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1056964 RingCT/type: yes/0
Extra: 018c5d6ad2e8739009e4d3c347396299dde0e544aa064ef3e30fae4a84763a4bcd021100000172ecf20436000000000000000000

1 output(s) for total of 161.944321012000 dcy

stealth address amount amount idx
00: 9dc5b14579cb1c36e305af080867216379c6832c65d3a30ecdb6bf81855d6171 161.944321012000 332636 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": 174644, "vin": [ { "gen": { "height": 174634 } } ], "vout": [ { "amount": 161944321012, "target": { "key": "9dc5b14579cb1c36e305af080867216379c6832c65d3a30ecdb6bf81855d6171" } } ], "extra": [ 1, 140, 93, 106, 210, 232, 115, 144, 9, 228, 211, 195, 71, 57, 98, 153, 221, 224, 229, 68, 170, 6, 78, 243, 227, 15, 174, 74, 132, 118, 58, 75, 205, 2, 17, 0, 0, 1, 114, 236, 242, 4, 54, 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