Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 964132931e7690784e5f2b555aa908cfda2b3a2d3b8627b07a60a888e17ee7a8

Tx prefix hash: c0de393300960e01f1c24d4c4649b142e3d5b7598d56261d9731088a1e8d5a82
Tx public key: 38935edcd405e5e3d9ec58b0fcdf8d39d1c769ba92abc17d03cda34658195738
Timestamp: 1736977207 Timestamp [UCT]: 2025-01-15 21:40:07 Age [y:d:h:m:s]: 00:154:12:53:52
Block: 1198151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110142 RingCT/type: yes/0
Extra: 0138935edcd405e5e3d9ec58b0fcdf8d39d1c769ba92abc17d03cda34658195738021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f07956cdad965b4db77c727024ad2d3038754dc2592f0cc74821c30c53f2761e 0.600000000000 1684770 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": 1198161, "vin": [ { "gen": { "height": 1198151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f07956cdad965b4db77c727024ad2d3038754dc2592f0cc74821c30c53f2761e" } } ], "extra": [ 1, 56, 147, 94, 220, 212, 5, 229, 227, 217, 236, 88, 176, 252, 223, 141, 57, 209, 199, 105, 186, 146, 171, 193, 125, 3, 205, 163, 70, 88, 25, 87, 56, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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