Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8aa0fb9012dd745c62d497d743c8147a0c990ab8e51d74406b8148024b06ec

Tx prefix hash: 968e114f1d17b4c4f57ec422674e77d553ea4d7e61bb994247636e540c64eddb
Tx public key: 74dcd9e01412fc4b096ac6f41510cc7feb7b8ddd3759040c6e08b00fe6931c55
Timestamp: 1717586184 Timestamp [UCT]: 2024-06-05 11:16:24 Age [y:d:h:m:s]: 00:148:04:04:06
Block: 1037554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106043 RingCT/type: yes/0
Extra: 0174dcd9e01412fc4b096ac6f41510cc7feb7b8ddd3759040c6e08b00fe6931c55021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea07e3adaee7cd607ce34e9dce0488b078939b6a9697265b0efb89b4f88862bb 0.600000000000 1506099 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": 1037564, "vin": [ { "gen": { "height": 1037554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea07e3adaee7cd607ce34e9dce0488b078939b6a9697265b0efb89b4f88862bb" } } ], "extra": [ 1, 116, 220, 217, 224, 20, 18, 252, 75, 9, 106, 198, 244, 21, 16, 204, 127, 235, 123, 141, 221, 55, 89, 4, 12, 110, 8, 176, 15, 230, 147, 28, 85, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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