Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1138f058ae30d3e7090f9c907b8ddac524a5649fdd375013aecaee15645487ae

Tx prefix hash: bab99818de673c09d656b7b54f770000460f15508f065d208fa44bd64a4f2f1f
Tx public key: 2e6778a801c571cdfdcc4c1a8779d27210ecf8cd1ad6b1c26cf20381c61ff4f8
Timestamp: 1764052325 Timestamp [UCT]: 2025-11-25 06:32:05 Age [y:d:h:m:s]: 00:001:07:46:33
Block: 1419641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 947 RingCT/type: yes/0
Extra: 012e6778a801c571cdfdcc4c1a8779d27210ecf8cd1ad6b1c26cf20381c61ff4f80211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4996af45d5aa35b6a0ff8d1a56ee3e8a2e1f10bb948d86efcb5c1588e139e7e9 0.600000000000 1908178 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": 1419651, "vin": [ { "gen": { "height": 1419641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4996af45d5aa35b6a0ff8d1a56ee3e8a2e1f10bb948d86efcb5c1588e139e7e9" } } ], "extra": [ 1, 46, 103, 120, 168, 1, 197, 113, 205, 253, 204, 76, 26, 135, 121, 210, 114, 16, 236, 248, 205, 26, 214, 177, 194, 108, 242, 3, 129, 198, 31, 244, 248, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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