Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2bf2e87c6264af26c83b412ae6655090ae6e3a8455df47688734d181e14e9f

Tx prefix hash: 58d2dd3fb66e3455aadadb67dfe3c7551fda7ec1269a79d5ea36697095d4d387
Tx public key: da552a853991e8e9199c96dea715183edbaa924e76b911d4b3a89de50923a3e1
Timestamp: 1747499920 Timestamp [UCT]: 2025-05-17 16:38:40 Age [y:d:h:m:s]: 00:144:10:58:36
Block: 1285007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100896 RingCT/type: yes/0
Extra: 01da552a853991e8e9199c96dea715183edbaa924e76b911d4b3a89de50923a3e10211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941c6068d41d34f12f61efcd18da1c2b589d06a7e39cc3bb70b0598db4e9877c 0.600000000000 1772470 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": 1285017, "vin": [ { "gen": { "height": 1285007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941c6068d41d34f12f61efcd18da1c2b589d06a7e39cc3bb70b0598db4e9877c" } } ], "extra": [ 1, 218, 85, 42, 133, 57, 145, 232, 233, 25, 156, 150, 222, 167, 21, 24, 62, 219, 170, 146, 78, 118, 185, 17, 212, 179, 168, 157, 229, 9, 35, 163, 225, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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