Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b35dd071aeea3c5bd832925083de8e3abce2e1f72f667fdafcdc9665c54e35ff

Tx prefix hash: a82ccb4d5cd12afb4bd5fc2abbcc2f99ba3d38e447f218201aded8175a17efed
Tx public key: 24d258c2fccba9461930ed8cb0bf72d8e5109e11497ec07c0e33c3c71497ca60
Timestamp: 1716751932 Timestamp [UCT]: 2024-05-26 19:32:12 Age [y:d:h:m:s]: 01:161:19:36:17
Block: 1030642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374221 RingCT/type: yes/0
Extra: 0124d258c2fccba9461930ed8cb0bf72d8e5109e11497ec07c0e33c3c71497ca600211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3890e1c1c7cb00058b534fbf53312febe7eabd5c4afea983b377410a161bc77 0.600000000000 1498899 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": 1030652, "vin": [ { "gen": { "height": 1030642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3890e1c1c7cb00058b534fbf53312febe7eabd5c4afea983b377410a161bc77" } } ], "extra": [ 1, 36, 210, 88, 194, 252, 203, 169, 70, 25, 48, 237, 140, 176, 191, 114, 216, 229, 16, 158, 17, 73, 126, 192, 124, 14, 51, 195, 199, 20, 151, 202, 96, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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