Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d032600515f4c090a1c420d55e2704cfbd27b1e4f07131b946b8fa9c8b3671f6

Tx prefix hash: 1981a08e0d779b93be9c3a878af2c9c9aa86c3130bf759b49804a7396f77988f
Tx public key: 1f7d01c859dce70945a38e6b4bb1da372163943eb2fac518fab42f3a56c5d3dc
Timestamp: 1750780747 Timestamp [UCT]: 2025-06-24 15:59:07 Age [y:d:h:m:s]: 00:149:12:05:30
Block: 1311919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104773 RingCT/type: yes/0
Extra: 011f7d01c859dce70945a38e6b4bb1da372163943eb2fac518fab42f3a56c5d3dc02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c2438e36d338a8187059acfbbfc0df8a7bdffe6ed75d3d991136c0f09cf5396 0.600000000000 1799548 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": 1311929, "vin": [ { "gen": { "height": 1311919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c2438e36d338a8187059acfbbfc0df8a7bdffe6ed75d3d991136c0f09cf5396" } } ], "extra": [ 1, 31, 125, 1, 200, 89, 220, 231, 9, 69, 163, 142, 107, 75, 177, 218, 55, 33, 99, 148, 62, 178, 250, 197, 24, 250, 180, 47, 58, 86, 197, 211, 220, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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