Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d85c56f9d5d12f01469792c2ffa85b7e84954511eb643147cd7271bc8d785fb

Tx prefix hash: 45361c80c0b2abba7c801c4c37375e39e54a0565356468c4767ddd45ef0a1709
Tx public key: 7f3bd610f853853e8f28aa9c605a93e678bde06fc5fe293272c9bf96bd2c0e3a
Timestamp: 1755596289 Timestamp [UCT]: 2025-08-19 09:38:09 Age [y:d:h:m:s]: 00:092:04:06:22
Block: 1349768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65788 RingCT/type: yes/0
Extra: 017f3bd610f853853e8f28aa9c605a93e678bde06fc5fe293272c9bf96bd2c0e3a021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ec60f1a631369a318e2865de4cfa09fef0faad3b3d44436b2f6233403927ac 0.600000000000 1837703 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": 1349778, "vin": [ { "gen": { "height": 1349768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ec60f1a631369a318e2865de4cfa09fef0faad3b3d44436b2f6233403927ac" } } ], "extra": [ 1, 127, 59, 214, 16, 248, 83, 133, 62, 143, 40, 170, 156, 96, 90, 147, 230, 120, 189, 224, 111, 197, 254, 41, 50, 114, 201, 191, 150, 189, 44, 14, 58, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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