Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6589fb058431b4d1151be584ffb8bf0fe3ef5928be0eca6ed459326acc1431c0

Tx prefix hash: ff8f2b6996f8a893e70566f8b12ae841e2b8c099f77c73bbc4ac920ad0021253
Tx public key: a9a8889863fdf01125a31381329ed505c3e5a31a108d47ba5a8dacd279a18d43
Timestamp: 1718570537 Timestamp [UCT]: 2024-06-16 20:42:17 Age [y:d:h:m:s]: 00:221:17:54:20
Block: 1045717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158630 RingCT/type: yes/0
Extra: 01a9a8889863fdf01125a31381329ed505c3e5a31a108d47ba5a8dacd279a18d430211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd1139cd292d5ac224c194675c6b4c66879eb93d9ba3e0ec522099fa17b7922c 0.600000000000 1515364 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": 1045727, "vin": [ { "gen": { "height": 1045717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd1139cd292d5ac224c194675c6b4c66879eb93d9ba3e0ec522099fa17b7922c" } } ], "extra": [ 1, 169, 168, 136, 152, 99, 253, 240, 17, 37, 163, 19, 129, 50, 158, 213, 5, 195, 229, 163, 26, 16, 141, 71, 186, 90, 141, 172, 210, 121, 161, 141, 67, 2, 17, 0, 0, 0, 1, 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