Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 625e8c2ea3bb39b1b0503b47ca4e90be983dab362ae4fae6673334e5a195f519

Tx prefix hash: 058c530690e69193255ade6b01474b185863d7b6566f4692a9182f42532eca7c
Tx public key: 189bf64a952a661bf1e9beb7cf8e049a5f8db40f53011db1ed8c1afc2dc56534
Timestamp: 1735256661 Timestamp [UCT]: 2024-12-26 23:44:21 Age [y:d:h:m:s]: 00:089:05:39:55
Block: 1183921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63542 RingCT/type: yes/0
Extra: 01189bf64a952a661bf1e9beb7cf8e049a5f8db40f53011db1ed8c1afc2dc565340211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c9db722864f776af4ae998fe9cc9ef78c81a441ccf4314f1702def4f1abd46 0.600000000000 1670370 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": 1183931, "vin": [ { "gen": { "height": 1183921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c9db722864f776af4ae998fe9cc9ef78c81a441ccf4314f1702def4f1abd46" } } ], "extra": [ 1, 24, 155, 246, 74, 149, 42, 102, 27, 241, 233, 190, 183, 207, 142, 4, 154, 95, 141, 180, 15, 83, 1, 29, 177, 237, 140, 26, 252, 45, 197, 101, 52, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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