Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238ac342912c4f2d8d519b62f2f292467adb627760a9f5bcf808bb6131a947ee

Tx prefix hash: 5f25cbc035d0c36ada1324dca436e85e9fd7c4e4cac8c2d5ecede95e277f7e7a
Tx public key: e4dc4361c6e827edce0f380759553bee98eed81031277bab5add9a88d34af6ba
Timestamp: 1732178840 Timestamp [UCT]: 2024-11-21 08:47:20 Age [y:d:h:m:s]: 00:175:13:16:45
Block: 1158425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125308 RingCT/type: yes/0
Extra: 01e4dc4361c6e827edce0f380759553bee98eed81031277bab5add9a88d34af6ba021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91d4ae0d19a95f0681a3893b719ddeead030337d767d93bb1346920f49efb70 0.600000000000 1644054 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": 1158435, "vin": [ { "gen": { "height": 1158425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91d4ae0d19a95f0681a3893b719ddeead030337d767d93bb1346920f49efb70" } } ], "extra": [ 1, 228, 220, 67, 97, 198, 232, 39, 237, 206, 15, 56, 7, 89, 85, 59, 238, 152, 238, 216, 16, 49, 39, 123, 171, 90, 221, 154, 136, 211, 74, 246, 186, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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