Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9eb1968d4a1b173e7d93fd2e9c859c2c0f0b34236dcd239b0c5737539b54b53

Tx prefix hash: 8d4b9648dcfdf015789e08d38358dcb30328b9165115dc0a995ee17a691e76b0
Tx public key: 560c799dbe8f05067a0be27c3172a987c93b61531472d9f74b33a56cca5ef417
Timestamp: 1699104464 Timestamp [UCT]: 2023-11-04 13:27:44 Age [y:d:h:m:s]: 02:003:10:50:31
Block: 884568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521989 RingCT/type: yes/0
Extra: 01560c799dbe8f05067a0be27c3172a987c93b61531472d9f74b33a56cca5ef41702110000000775e3f0e9000000000000000000

1 output(s) for total of 0.719546757000 dcy

stealth address amount amount idx
00: 7c04e61b9b49e64cb6938324744028e4f13e0a2781351d30343766e5c03ca1c7 0.719546757000 1340313 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": 884578, "vin": [ { "gen": { "height": 884568 } } ], "vout": [ { "amount": 719546757, "target": { "key": "7c04e61b9b49e64cb6938324744028e4f13e0a2781351d30343766e5c03ca1c7" } } ], "extra": [ 1, 86, 12, 121, 157, 190, 143, 5, 6, 122, 11, 226, 124, 49, 114, 169, 135, 201, 59, 97, 83, 20, 114, 217, 247, 75, 51, 165, 108, 202, 94, 244, 23, 2, 17, 0, 0, 0, 7, 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