Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37875f357ffe6436bd6ce51f19e05d2f6be8c097a18857023f9fc4518071621d

Tx prefix hash: e8ae532c574931db2a71d2760824e5f3ffd9c0425f0134616f4d50befd15d6e0
Tx public key: b9b7b8b8d3ce7cdb72181cf9f7ca3d9beac636e37e18194a3b9ed7b961665dc7
Timestamp: 1675337520 Timestamp [UCT]: 2023-02-02 11:32:00 Age [y:d:h:m:s]: 02:023:19:25:20
Block: 688158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538604 RingCT/type: yes/0
Extra: 01b9b7b8b8d3ce7cdb72181cf9f7ca3d9beac636e37e18194a3b9ed7b961665dc70211000000025029cbac000000000000000000

1 output(s) for total of 3.219932804000 dcy

stealth address amount amount idx
00: fb57445b86bc3363465ec9d7ac14ef761fb0e8321515d8ffc7e9edbebb8f8c20 3.219932804000 1130762 of 0

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": 688168, "vin": [ { "gen": { "height": 688158 } } ], "vout": [ { "amount": 3219932804, "target": { "key": "fb57445b86bc3363465ec9d7ac14ef761fb0e8321515d8ffc7e9edbebb8f8c20" } } ], "extra": [ 1, 185, 183, 184, 184, 211, 206, 124, 219, 114, 24, 28, 249, 247, 202, 61, 155, 234, 198, 54, 227, 126, 24, 25, 74, 59, 158, 215, 185, 97, 102, 93, 199, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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