Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99ab41b0379c2e4f407b0bfd002b7f3a32de273a7a508f70d2caf5337ad0c7c0

Tx prefix hash: 008d68108aabdfb790ba4f46eacd41e45704be8678f9c2e48179c6078413579a
Tx public key: da68c89778e6d7cca33dfbd4be52e10ddb0d5641b0b19fe89d1becfac751830a
Timestamp: 1609130308 Timestamp [UCT]: 2020-12-28 04:38:28 Age [y:d:h:m:s]: 04:073:17:23:13
Block: 170637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065906 RingCT/type: yes/0
Extra: 01da68c89778e6d7cca33dfbd4be52e10ddb0d5641b0b19fe89d1becfac751830a02110000002edf1e48bb000000000000000000

1 output(s) for total of 166.964631686000 dcy

stealth address amount amount idx
00: f61170d779e660c9209295c457a51a61cce3abd780aea2eb18b81faff12884ac 166.964631686000 320238 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": 170647, "vin": [ { "gen": { "height": 170637 } } ], "vout": [ { "amount": 166964631686, "target": { "key": "f61170d779e660c9209295c457a51a61cce3abd780aea2eb18b81faff12884ac" } } ], "extra": [ 1, 218, 104, 200, 151, 120, 230, 215, 204, 163, 61, 251, 212, 190, 82, 225, 13, 219, 13, 86, 65, 176, 177, 159, 232, 157, 27, 236, 250, 199, 81, 131, 10, 2, 17, 0, 0, 0, 46, 223, 30, 72, 187, 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