Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9f6a7fcfd5271ad46f9b10c177de727f0fd341c3c4c0d5cbfbc5e9a64b71e8

Tx prefix hash: c31c035cc9ed4dc8940af237f7051101ac1686bbdfa12c3e4c002351ef555fa9
Tx public key: 4d5e8278b675784630da468e6e42897b8400d8f73f73a2dca70f97bb7e8e0572
Timestamp: 1726232496 Timestamp [UCT]: 2024-09-13 13:01:36 Age [y:d:h:m:s]: 00:162:16:00:43
Block: 1109222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116050 RingCT/type: yes/0
Extra: 014d5e8278b675784630da468e6e42897b8400d8f73f73a2dca70f97bb7e8e057202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf94362d7ee8a5e5e412ea087edc0c6b65af54cc791606cb84f5fcd617cb7a9 0.600000000000 1587395 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": 1109232, "vin": [ { "gen": { "height": 1109222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf94362d7ee8a5e5e412ea087edc0c6b65af54cc791606cb84f5fcd617cb7a9" } } ], "extra": [ 1, 77, 94, 130, 120, 182, 117, 120, 70, 48, 218, 70, 142, 110, 66, 137, 123, 132, 0, 216, 247, 63, 115, 162, 220, 167, 15, 151, 187, 126, 142, 5, 114, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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