Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b035756e3adf8832fa820bbc9451d54a79d7c88eacd1c0b17860ff2e85c7dd9

Tx prefix hash: 3fed5da680c07e8d3c3a1d148a10e8ebde7ffec34c301de28248334fd3506fef
Tx public key: d644c7fc6eedcbdc1fcf55ff35363195a72bd61e17c86b31af4f8ba5324794b1
Timestamp: 1702894558 Timestamp [UCT]: 2023-12-18 10:15:58 Age [y:d:h:m:s]: 01:155:08:16:17
Block: 915736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372204 RingCT/type: yes/0
Extra: 01d644c7fc6eedcbdc1fcf55ff35363195a72bd61e17c86b31af4f8ba5324794b1021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d07aabee807180a3a8c679f071f572a3c8e1e55a14b13c0bc4f9e2037047e8d 0.600000000000 1373160 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": 915746, "vin": [ { "gen": { "height": 915736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d07aabee807180a3a8c679f071f572a3c8e1e55a14b13c0bc4f9e2037047e8d" } } ], "extra": [ 1, 214, 68, 199, 252, 110, 237, 203, 220, 31, 207, 85, 255, 53, 54, 49, 149, 167, 43, 214, 30, 23, 200, 107, 49, 175, 79, 139, 165, 50, 71, 148, 177, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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