Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c91b88e881758671f48c7fc46f1eca65288611a8c6fba74501d55316d2817a1

Tx prefix hash: 368072e39a5e56753d65e8e3238fd6a00490175e1de6b4e2a3da5cfa859f1b11
Tx public key: 6731e827d6fcd0254d88f6d5a012b24dc767344eb244f9bb3f35cb8e2b05aa9f
Timestamp: 1705201883 Timestamp [UCT]: 2024-01-14 03:11:23 Age [y:d:h:m:s]: 01:070:02:18:55
Block: 934845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311195 RingCT/type: yes/0
Extra: 016731e827d6fcd0254d88f6d5a012b24dc767344eb244f9bb3f35cb8e2b05aa9f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7c377ecfbfab4c4a67f341feee4353b61407643ace329a4d9efdf9ca0a492ce 0.600000000000 1392861 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": 934855, "vin": [ { "gen": { "height": 934845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c377ecfbfab4c4a67f341feee4353b61407643ace329a4d9efdf9ca0a492ce" } } ], "extra": [ 1, 103, 49, 232, 39, 214, 252, 208, 37, 77, 136, 246, 213, 160, 18, 178, 77, 199, 103, 52, 78, 178, 68, 249, 187, 63, 53, 203, 142, 43, 5, 170, 159, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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