Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68418572c7292e2fe87dd962abf8a55ff5a4621fa755208430d5c8f8476e5c70

Tx prefix hash: e92354e21691a9f629bf83b54cb0659cb0433c53b9e654a22b9edbbde00a7c99
Tx public key: bd9545adb6e7954764a14d2d67295078e48d48b0c40a1ff31243109f25ac11d7
Timestamp: 1745124519 Timestamp [UCT]: 2025-04-20 04:48:39 Age [y:d:h:m:s]: 00:212:12:41:38
Block: 1265330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149631 RingCT/type: yes/0
Extra: 01bd9545adb6e7954764a14d2d67295078e48d48b0c40a1ff31243109f25ac11d7021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdedbf63d91479d5ae4ce12d92b95c6736bb59f9c39df9addb36de3fa6e0442c 0.600000000000 1752537 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": 1265340, "vin": [ { "gen": { "height": 1265330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdedbf63d91479d5ae4ce12d92b95c6736bb59f9c39df9addb36de3fa6e0442c" } } ], "extra": [ 1, 189, 149, 69, 173, 182, 231, 149, 71, 100, 161, 77, 45, 103, 41, 80, 120, 228, 141, 72, 176, 196, 10, 31, 243, 18, 67, 16, 159, 37, 172, 17, 215, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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