Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb4ea668d38aed288023777c307e887c49d7ca1d4bebc3efd73deacc231ba6f

Tx prefix hash: 4a0e831690411c7e180bd3fe368297201f7a10f312651e3417f09e937d888cd6
Tx public key: 1b3e47babf5589d7c1e8bdd1c29155d3b7296529898bdbea5aa47ad448a81593
Timestamp: 1738041950 Timestamp [UCT]: 2025-01-28 05:25:50 Age [y:d:h:m:s]: 00:144:19:57:35
Block: 1206735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103388 RingCT/type: yes/0
Extra: 011b3e47babf5589d7c1e8bdd1c29155d3b7296529898bdbea5aa47ad448a815930211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd074bc5fe441c2a69a46f225f654446b82dfac17e336f6f7f1ab660ad5dc02 0.600000000000 1693448 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": 1206745, "vin": [ { "gen": { "height": 1206735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd074bc5fe441c2a69a46f225f654446b82dfac17e336f6f7f1ab660ad5dc02" } } ], "extra": [ 1, 27, 62, 71, 186, 191, 85, 137, 215, 193, 232, 189, 209, 194, 145, 85, 211, 183, 41, 101, 41, 137, 139, 219, 234, 90, 164, 122, 212, 72, 168, 21, 147, 2, 17, 0, 0, 0, 1, 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