Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d82fe206e87a7a06bd75196da9434d0c76d0189c4b0c4d4bce0f2abdfe8b000

Tx prefix hash: d14b59aa0d768417a62285489206144623481a438abb00afd143dafebc5ae2a2
Tx public key: 3c8f37ac4709ab3fa790a5ec8a3fb9ee638a812d784dede1e9b32398d63e80b4
Timestamp: 1738596084 Timestamp [UCT]: 2025-02-03 15:21:24 Age [y:d:h:m:s]: 00:290:06:25:17
Block: 1211278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205233 RingCT/type: yes/0
Extra: 013c8f37ac4709ab3fa790a5ec8a3fb9ee638a812d784dede1e9b32398d63e80b402110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ef0a1b96d5caa92db044610f9067b6b27c69115dfa80c8e9cf97405d485dbba 0.600000000000 1698037 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": 1211288, "vin": [ { "gen": { "height": 1211278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ef0a1b96d5caa92db044610f9067b6b27c69115dfa80c8e9cf97405d485dbba" } } ], "extra": [ 1, 60, 143, 55, 172, 71, 9, 171, 63, 167, 144, 165, 236, 138, 63, 185, 238, 99, 138, 129, 45, 120, 77, 237, 225, 233, 179, 35, 152, 214, 62, 128, 180, 2, 17, 0, 0, 0, 10, 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