Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 753de55a5b8a08e1368d9b377f175b4f9e124a804f32a61749105d99a851aa81

Tx prefix hash: e840561b180e0505899d020951847fa6e082e3c3791cbf59673e0be080b62716
Tx public key: 9fd95e55024ac3969d439fe53a73e8755aaea72991bfeecae33871203bb9f848
Timestamp: 1608745237 Timestamp [UCT]: 2020-12-23 17:40:37 Age [y:d:h:m:s]: 04:116:15:32:03
Block: 167920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096123 RingCT/type: yes/0
Extra: 019fd95e55024ac3969d439fe53a73e8755aaea72991bfeecae33871203bb9f8480211000002974ea414e5000000000000000000

1 output(s) for total of 170.462855808000 dcy

stealth address amount amount idx
00: 8263d6ab22d6dc365f93d7a1d088094c358f42bd32b5fb0c7defd00e8f5f8c71 170.462855808000 310639 of 0

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": 167930, "vin": [ { "gen": { "height": 167920 } } ], "vout": [ { "amount": 170462855808, "target": { "key": "8263d6ab22d6dc365f93d7a1d088094c358f42bd32b5fb0c7defd00e8f5f8c71" } } ], "extra": [ 1, 159, 217, 94, 85, 2, 74, 195, 150, 157, 67, 159, 229, 58, 115, 232, 117, 90, 174, 167, 41, 145, 191, 238, 202, 227, 56, 113, 32, 59, 185, 248, 72, 2, 17, 0, 0, 2, 151, 78, 164, 20, 229, 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