Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56a78fa0b14863b923d5e6883b0a2988d32c0ffa7bb601f85a4cea81b6dab21

Tx prefix hash: 564fa201962dcba848c0f8a816acdff352c1d24049fcbcdbd7bf488e43523349
Tx public key: de8d51a7ee2b882925596148ea229f39916326e3b4149d998c176829c5bce56f
Timestamp: 1694837673 Timestamp [UCT]: 2023-09-16 04:14:33 Age [y:d:h:m:s]: 01:130:11:01:48
Block: 849132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354518 RingCT/type: yes/0
Extra: 01de8d51a7ee2b882925596148ea229f39916326e3b4149d998c176829c5bce56f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.942916532000 dcy

stealth address amount amount idx
00: a91e6bc9fc2cd861a7e87f425282473867e42e3b069882f684dfa4df624d983e 0.942916532000 1302776 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": 849142, "vin": [ { "gen": { "height": 849132 } } ], "vout": [ { "amount": 942916532, "target": { "key": "a91e6bc9fc2cd861a7e87f425282473867e42e3b069882f684dfa4df624d983e" } } ], "extra": [ 1, 222, 141, 81, 167, 238, 43, 136, 41, 37, 89, 97, 72, 234, 34, 159, 57, 145, 99, 38, 227, 180, 20, 157, 153, 140, 23, 104, 41, 197, 188, 229, 111, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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