Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b64e442d24872cd08720305af9a33d2d2dd9463e675a7ff4491e373b1c6b75e8

Tx prefix hash: 839af8975e8cfd7d4f2c6235f2fcd96c0de4a68d33baa35c6644066f40020e03
Tx public key: 20d84ca0b7f80b8e0a5aac6c5bd1dbd6ead6a0fbdc9354a087fa04f09dca9074
Timestamp: 1730538235 Timestamp [UCT]: 2024-11-02 09:03:55 Age [y:d:h:m:s]: 00:022:01:30:29
Block: 1144832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15792 RingCT/type: yes/0
Extra: 0120d84ca0b7f80b8e0a5aac6c5bd1dbd6ead6a0fbdc9354a087fa04f09dca90740211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1a24b1fcc5c57cae4aed698ba47147ba01f94ed3a246adca6d2083445b7d8ea 0.600000000000 1629159 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": 1144842, "vin": [ { "gen": { "height": 1144832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1a24b1fcc5c57cae4aed698ba47147ba01f94ed3a246adca6d2083445b7d8ea" } } ], "extra": [ 1, 32, 216, 76, 160, 183, 248, 11, 142, 10, 90, 172, 108, 91, 209, 219, 214, 234, 214, 160, 251, 220, 147, 84, 160, 135, 250, 4, 240, 157, 202, 144, 116, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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