Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab81b61c1cd20fdf23c9f9eae455326db0fb2e7973e0113c628d809a8c9f9914

Tx prefix hash: 46b483e93834ce7290d1477131008aa7eee5aedfd0c8930b802450e4f35bb964
Tx public key: 9d65627e1ad0eec3d4597eb45a767a774c33be1055d1efa9d0093b596eaf176b
Timestamp: 1734950396 Timestamp [UCT]: 2024-12-23 10:39:56 Age [y:d:h:m:s]: 00:176:21:52:50
Block: 1181412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126130 RingCT/type: yes/0
Extra: 019d65627e1ad0eec3d4597eb45a767a774c33be1055d1efa9d0093b596eaf176b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f582055cf3d54407152baeb6e116987c2911168b40ba34b7bd5b7add7e56c5b6 0.600000000000 1667833 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": 1181422, "vin": [ { "gen": { "height": 1181412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f582055cf3d54407152baeb6e116987c2911168b40ba34b7bd5b7add7e56c5b6" } } ], "extra": [ 1, 157, 101, 98, 126, 26, 208, 238, 195, 212, 89, 126, 180, 90, 118, 122, 119, 76, 51, 190, 16, 85, 209, 239, 169, 208, 9, 59, 89, 110, 175, 23, 107, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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