Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ad8671f2f7ad7299996cb31620798f4a8cedd9e5f6ae500b306aa4aef0572e

Tx prefix hash: 8887e9e0e2e9872b7d31abb89624ab2c9d4412009aa40d6074518bd59bda5b06
Tx public key: 224aa26a991e63ba4501be6ddecc548c44f5e13f87132095cf745c7b05e452a6
Timestamp: 1745251074 Timestamp [UCT]: 2025-04-21 15:57:54 Age [y:d:h:m:s]: 00:211:17:40:23
Block: 1266388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149044 RingCT/type: yes/0
Extra: 01224aa26a991e63ba4501be6ddecc548c44f5e13f87132095cf745c7b05e452a6021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f78fb71f7d8f5d10263b9276b0c9f93769d4ef3d160f003a648c5db503abbcf3 0.600000000000 1753609 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": 1266398, "vin": [ { "gen": { "height": 1266388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f78fb71f7d8f5d10263b9276b0c9f93769d4ef3d160f003a648c5db503abbcf3" } } ], "extra": [ 1, 34, 74, 162, 106, 153, 30, 99, 186, 69, 1, 190, 109, 222, 204, 84, 140, 68, 245, 225, 63, 135, 19, 32, 149, 207, 116, 92, 123, 5, 228, 82, 166, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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