Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88250d388ddab691542eae6e05ef7dbfabacf73e527d13b971a08b1ddf4e8cdb

Tx prefix hash: 339ba636d12a7db701120884eee52df62d8280f85a5c91739559b87d59475b93
Tx public key: dc2bc5e670a5b518cd972ffc590d38eb9d91d951c41304ab3a2e7896b582b7c1
Timestamp: 1704236183 Timestamp [UCT]: 2024-01-02 22:56:23 Age [y:d:h:m:s]: 01:334:03:16:57
Block: 926859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497666 RingCT/type: yes/0
Extra: 01dc2bc5e670a5b518cd972ffc590d38eb9d91d951c41304ab3a2e7896b582b7c10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df8a2b38261e9936591691e9911764b3f39b0dcaccae52534fe823f894466121 0.600000000000 1384657 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": 926869, "vin": [ { "gen": { "height": 926859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df8a2b38261e9936591691e9911764b3f39b0dcaccae52534fe823f894466121" } } ], "extra": [ 1, 220, 43, 197, 230, 112, 165, 181, 24, 205, 151, 47, 252, 89, 13, 56, 235, 157, 145, 217, 81, 196, 19, 4, 171, 58, 46, 120, 150, 181, 130, 183, 193, 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