Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a62edba920a4bae4e25086572febb54ba3513a7b7edc123c9a225236975aada

Tx prefix hash: d723fe962c4874e91169864d5c12391700f9a4a9a56d29f47ece1ff68eba761e
Tx public key: fc37bf9c41c454a95b8816eec5d0543835eee5c30008cae40ea8fad3e27b9043
Timestamp: 1714073863 Timestamp [UCT]: 2024-04-25 19:37:43 Age [y:d:h:m:s]: 01:019:02:49:44
Block: 1008419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274623 RingCT/type: yes/0
Extra: 01fc37bf9c41c454a95b8816eec5d0543835eee5c30008cae40ea8fad3e27b904302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dfce3802b50d1b35a218ae22b2ac157b782129128dac1d4b2c82e3d5f4c3c37 0.600000000000 1469889 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": 1008429, "vin": [ { "gen": { "height": 1008419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dfce3802b50d1b35a218ae22b2ac157b782129128dac1d4b2c82e3d5f4c3c37" } } ], "extra": [ 1, 252, 55, 191, 156, 65, 196, 84, 169, 91, 136, 22, 238, 197, 208, 84, 56, 53, 238, 229, 195, 0, 8, 202, 228, 14, 168, 250, 211, 226, 123, 144, 67, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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