Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d94571f64df79e212a0b053b7be5972e943b67ce16f027f2add14b858e7076c

Tx prefix hash: d211461a6b6293f855ea62f679d591f405ac7b85f6ebf6bbaec14e0889a3624c
Tx public key: ed6618ad2742b28e10226910ca1fd4d8e2565a966347e7b81704b7f3e8aaab76
Timestamp: 1745726981 Timestamp [UCT]: 2025-04-27 04:09:41 Age [y:d:h:m:s]: 00:280:06:17:08
Block: 1270334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197930 RingCT/type: yes/0
Extra: 01ed6618ad2742b28e10226910ca1fd4d8e2565a966347e7b81704b7f3e8aaab7602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cd49d00358477241a6edce69a8b6d75e627e153f343aa948db6aa0214e4c159 0.600000000000 1757575 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": 1270344, "vin": [ { "gen": { "height": 1270334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd49d00358477241a6edce69a8b6d75e627e153f343aa948db6aa0214e4c159" } } ], "extra": [ 1, 237, 102, 24, 173, 39, 66, 178, 142, 16, 34, 105, 16, 202, 31, 212, 216, 226, 86, 90, 150, 99, 71, 231, 184, 23, 4, 183, 243, 232, 170, 171, 118, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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