Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e33761693440dd07e4bfa9a203ab639f87047776366e592d92be584b742eda8

Tx prefix hash: 08b8f21f2c2d741630ccdee9baef5fb628c499773fef5737ce16573cbacbaee2
Tx public key: 17c9b6e3d9abc3b7e74e7175dce9506017fcf53ba46c7971bc4fa2daa237219e
Timestamp: 1698334132 Timestamp [UCT]: 2023-10-26 15:28:52 Age [y:d:h:m:s]: 01:144:19:55:08
Block: 878155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364516 RingCT/type: yes/0
Extra: 0117c9b6e3d9abc3b7e74e7175dce9506017fcf53ba46c7971bc4fa2daa237219e02110000000f4b8f5122000000000000000000

1 output(s) for total of 0.755627858000 dcy

stealth address amount amount idx
00: 08c4f1415d12e8ef353189eefa0755a9d385b9d8f6767579ceaa69cb0e58c4dc 0.755627858000 1333571 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": 878165, "vin": [ { "gen": { "height": 878155 } } ], "vout": [ { "amount": 755627858, "target": { "key": "08c4f1415d12e8ef353189eefa0755a9d385b9d8f6767579ceaa69cb0e58c4dc" } } ], "extra": [ 1, 23, 201, 182, 227, 217, 171, 195, 183, 231, 78, 113, 117, 220, 233, 80, 96, 23, 252, 245, 59, 164, 108, 121, 113, 188, 79, 162, 218, 162, 55, 33, 158, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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