Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d96436a8faf94a0f05eb449e6bea4a8c61214d5b1ba07c6b79ca68521d9ad050

Tx prefix hash: d7a545c1bf628fecfd11794c09f4aaec504ecf3309f74c64b21774085d93845f
Tx public key: 6e36f272dd1e9fa7e7c177ee14332a1b62f3395507ba6526aada9379d4370756
Timestamp: 1709364408 Timestamp [UCT]: 2024-03-02 07:26:48 Age [y:d:h:m:s]: 01:069:14:38:47
Block: 969391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310763 RingCT/type: yes/0
Extra: 016e36f272dd1e9fa7e7c177ee14332a1b62f3395507ba6526aada9379d43707560211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a87364290db1fda7934a544e4ae7d46e3f4be39d9a90510c76ca11caa5bf9840 0.600000000000 1429220 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": 969401, "vin": [ { "gen": { "height": 969391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a87364290db1fda7934a544e4ae7d46e3f4be39d9a90510c76ca11caa5bf9840" } } ], "extra": [ 1, 110, 54, 242, 114, 221, 30, 159, 167, 231, 193, 119, 238, 20, 51, 42, 27, 98, 243, 57, 85, 7, 186, 101, 38, 170, 218, 147, 121, 212, 55, 7, 86, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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