Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cb540ee2551634cf871d77d045ea9c351331816329f15ee6c5df98d16a1307

Tx prefix hash: 20eb5ebb6ae083c7626e6f560d9ece34a6dd8c5d1e1be5a23da3199f6132a5d5
Tx public key: a4851c14870ed0cbf861723dfaeea635890b5f5ca2f4d0ef2c051aa17398e987
Timestamp: 1733041221 Timestamp [UCT]: 2024-12-01 08:20:21 Age [y:d:h:m:s]: 00:118:03:10:30
Block: 1165582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84223 RingCT/type: yes/0
Extra: 01a4851c14870ed0cbf861723dfaeea635890b5f5ca2f4d0ef2c051aa17398e987021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7d0e8273f5d14b55fb61ca75c2317d437cc7594c4612254c45aaff459eeadd 0.600000000000 1651257 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": 1165592, "vin": [ { "gen": { "height": 1165582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7d0e8273f5d14b55fb61ca75c2317d437cc7594c4612254c45aaff459eeadd" } } ], "extra": [ 1, 164, 133, 28, 20, 135, 14, 208, 203, 248, 97, 114, 61, 250, 238, 166, 53, 137, 11, 95, 92, 162, 244, 208, 239, 44, 5, 26, 161, 115, 152, 233, 135, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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