Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a507f69a12819cd5a9b9daeb4742b11ec1cc7e066deab020179a8c9de86515cd

Tx prefix hash: e0c5ce6a7cdc3e48038cccfd3b61a85c045e6c945d82c711b0469d2f530ee998
Tx public key: 53263b289be4a41a56598ab90803302fd3659ddbd0c4c81ce5b30cbafe6d0d8f
Timestamp: 1721979349 Timestamp [UCT]: 2024-07-26 07:35:49 Age [y:d:h:m:s]: 00:306:14:27:26
Block: 1073958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219084 RingCT/type: yes/0
Extra: 0153263b289be4a41a56598ab90803302fd3659ddbd0c4c81ce5b30cbafe6d0d8f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba13c998ce75aa2d771407977d9cdf5d0b19f68133b0bc6301e01ec9a283510 0.600000000000 1546467 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": 1073968, "vin": [ { "gen": { "height": 1073958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba13c998ce75aa2d771407977d9cdf5d0b19f68133b0bc6301e01ec9a283510" } } ], "extra": [ 1, 83, 38, 59, 40, 155, 228, 164, 26, 86, 89, 138, 185, 8, 3, 48, 47, 211, 101, 157, 219, 208, 196, 200, 28, 229, 179, 12, 186, 254, 109, 13, 143, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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