Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb993ae806f5f27c6d962b50df134e31164f7ec077dcf4d434b119009c1a050

Tx prefix hash: f39cb681b6db2ba43444b68c4041a8501bf3f7051457a259c85a8b27d3ddd737
Tx public key: 8e5fe226b54eb72bb32396c73ff6f141c9ee22ca595154b6f0e865789a215b50
Timestamp: 1704654844 Timestamp [UCT]: 2024-01-07 19:14:04 Age [y:d:h:m:s]: 01:101:19:33:26
Block: 930313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333900 RingCT/type: yes/0
Extra: 018e5fe226b54eb72bb32396c73ff6f141c9ee22ca595154b6f0e865789a215b500211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3472bc6435f02634846fde7dc1773103b434b0c5d3ebd27da1b7c65bed35ede1 0.600000000000 1388195 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": 930323, "vin": [ { "gen": { "height": 930313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3472bc6435f02634846fde7dc1773103b434b0c5d3ebd27da1b7c65bed35ede1" } } ], "extra": [ 1, 142, 95, 226, 38, 181, 78, 183, 43, 179, 35, 150, 199, 63, 246, 241, 65, 201, 238, 34, 202, 89, 81, 84, 182, 240, 232, 101, 120, 154, 33, 91, 80, 2, 17, 0, 0, 0, 5, 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