Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e225f7b48295e5d64d33cccd79071ad7e9bcd69a0dcb42902337db8f55ed70c4

Tx prefix hash: f61dca88395fe5353f7368a9070db1c046db1c5649e8f9a76203912cd113cbeb
Tx public key: 397ad1973d0efd4570cf06b8f0a6cac358b6ce65db14a0e734f14fe8d7a3a5a2
Timestamp: 1744916074 Timestamp [UCT]: 2025-04-17 18:54:34 Age [y:d:h:m:s]: 00:203:05:23:41
Block: 1263599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142958 RingCT/type: yes/0
Extra: 01397ad1973d0efd4570cf06b8f0a6cac358b6ce65db14a0e734f14fe8d7a3a5a20211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25af65cf789a56142b14a3e7ce8acbd7ff23ddd45fa4f24374885623ccb00b27 0.600000000000 1750790 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": 1263609, "vin": [ { "gen": { "height": 1263599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25af65cf789a56142b14a3e7ce8acbd7ff23ddd45fa4f24374885623ccb00b27" } } ], "extra": [ 1, 57, 122, 209, 151, 61, 14, 253, 69, 112, 207, 6, 184, 240, 166, 202, 195, 88, 182, 206, 101, 219, 20, 160, 231, 52, 241, 79, 232, 215, 163, 165, 162, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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