Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a53718b9f04db4affc7fa47dc672e15a81eb9f32ee7b6168dc60c3f941c76e7

Tx prefix hash: 0d98eb3fcc9c96a12f850f5f2bb631cbb01ec26bbb9436df985ad8e57e6ff3ec
Tx public key: 4a35a1ba5cb268dc035a76dde5afcc04a8db12d42d0235745372965fb8d87670
Timestamp: 1705826970 Timestamp [UCT]: 2024-01-21 08:49:30 Age [y:d:h:m:s]: 01:347:10:31:52
Block: 940019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507217 RingCT/type: yes/0
Extra: 014a35a1ba5cb268dc035a76dde5afcc04a8db12d42d0235745372965fb8d8767002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3954af3fec42411492187a5f51cbbdd087e621bb0cbaf8570ee76527a462c86b 0.600000000000 1398153 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": 940029, "vin": [ { "gen": { "height": 940019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3954af3fec42411492187a5f51cbbdd087e621bb0cbaf8570ee76527a462c86b" } } ], "extra": [ 1, 74, 53, 161, 186, 92, 178, 104, 220, 3, 90, 118, 221, 229, 175, 204, 4, 168, 219, 18, 212, 45, 2, 53, 116, 83, 114, 150, 95, 184, 216, 118, 112, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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