Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5740027726fc40eb5445dd78c7501dec2ce1727ac452b79ddd4d55fb0e0f8c5e

Tx prefix hash: 745accb3fbbd140dfd78a35e9f26f90a8e196f3fc35941316c648be8b13b4b9a
Tx public key: 4f9f68855b3c0edeb685928f3ddbf6931cadfbb66cff17bff002c304a5f44a85
Timestamp: 1750588976 Timestamp [UCT]: 2025-06-22 10:42:56 Age [y:d:h:m:s]: 00:151:11:45:03
Block: 1310401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106129 RingCT/type: yes/0
Extra: 014f9f68855b3c0edeb685928f3ddbf6931cadfbb66cff17bff002c304a5f44a850211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c8fad7c1d104ebd2f5d415d54460d748ead95593a8a19236b4aede37733d62d 0.600000000000 1798020 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": 1310411, "vin": [ { "gen": { "height": 1310401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c8fad7c1d104ebd2f5d415d54460d748ead95593a8a19236b4aede37733d62d" } } ], "extra": [ 1, 79, 159, 104, 133, 91, 60, 14, 222, 182, 133, 146, 143, 61, 219, 246, 147, 28, 173, 251, 182, 108, 255, 23, 191, 240, 2, 195, 4, 165, 244, 74, 133, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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