Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250ed28ffc9009fa046b96c33bd114cef28a0f0313b03bf013ef737b6dd9ea52

Tx prefix hash: d957e4a64fc072ad5d35a97f28e34834212a4dd22ba9b43810c290e5bd719ac1
Tx public key: ee4c4e5c8bc4f83c414f055a9a6234cb5388ffc763f7f28efd53c9ffa6273067
Timestamp: 1720987267 Timestamp [UCT]: 2024-07-14 20:01:07 Age [y:d:h:m:s]: 00:193:05:23:48
Block: 1065744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138210 RingCT/type: yes/0
Extra: 01ee4c4e5c8bc4f83c414f055a9a6234cb5388ffc763f7f28efd53c9ffa627306702110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a90dc076f386ffaaecffab955ec8fbe36a609fcf5bc54d634ff21fc24b6a49 0.600000000000 1536295 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": 1065754, "vin": [ { "gen": { "height": 1065744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a90dc076f386ffaaecffab955ec8fbe36a609fcf5bc54d634ff21fc24b6a49" } } ], "extra": [ 1, 238, 76, 78, 92, 139, 196, 248, 60, 65, 79, 5, 90, 154, 98, 52, 203, 83, 136, 255, 199, 99, 247, 242, 142, 253, 83, 201, 255, 166, 39, 48, 103, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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