Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e445c6831ea2d7c828fefaaa9268a8262aee21d4f5ef6565b61e05e74d18dc4d

Tx prefix hash: 6ff1a53770779e8e0e9a0c46e0e1338bf69edf6db2f40d19f6a5aca4af954d5d
Tx public key: 770b3be4036140287fbaea322ff5f5ac2cdb86168bce545a0e92e6cf352aca0b
Timestamp: 1727993225 Timestamp [UCT]: 2024-10-03 22:07:05 Age [y:d:h:m:s]: 01:041:06:32:21
Block: 1123824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287887 RingCT/type: yes/0
Extra: 01770b3be4036140287fbaea322ff5f5ac2cdb86168bce545a0e92e6cf352aca0b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ea0e145fb95bd310d729d9e581ba71507f7610e3819cd2f3db5fb8fec0eebe2 0.600000000000 1606359 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": 1123834, "vin": [ { "gen": { "height": 1123824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ea0e145fb95bd310d729d9e581ba71507f7610e3819cd2f3db5fb8fec0eebe2" } } ], "extra": [ 1, 119, 11, 59, 228, 3, 97, 64, 40, 127, 186, 234, 50, 47, 245, 245, 172, 44, 219, 134, 22, 139, 206, 84, 90, 14, 146, 230, 207, 53, 42, 202, 11, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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