Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8c28ce556ebb9ce25629f47e66ff513040fac9bd2264c3626a2e386ecdf0f3

Tx prefix hash: 3d9807436e87e1ff8b603f30d288e8fb3e3e99c055ba03d07eb0809b457a92d5
Tx public key: 94a8f65f42cd03d57e0144f32b22446cb7d4639c48d4923374f8d4735c0e0d71
Timestamp: 1735971419 Timestamp [UCT]: 2025-01-04 06:16:59 Age [y:d:h:m:s]: 00:095:21:14:04
Block: 1189849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68301 RingCT/type: yes/0
Extra: 0194a8f65f42cd03d57e0144f32b22446cb7d4639c48d4923374f8d4735c0e0d7102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a55659fe53b8a35980fc0748ea3a857d72dedb711b6dbd4df5afa807fe258787 0.600000000000 1676362 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": 1189859, "vin": [ { "gen": { "height": 1189849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a55659fe53b8a35980fc0748ea3a857d72dedb711b6dbd4df5afa807fe258787" } } ], "extra": [ 1, 148, 168, 246, 95, 66, 205, 3, 213, 126, 1, 68, 243, 43, 34, 68, 108, 183, 212, 99, 156, 72, 212, 146, 51, 116, 248, 212, 115, 92, 14, 13, 113, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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