Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e5574e943bcf0554a8fe38d5f6465c2f8a804bbe5fb52c918d1682798a3bfe2

Tx prefix hash: a257ebf807b042594f0f2a43ae89187a57fe164074053d0162c53f4ada6f8580
Tx public key: a740e2aa4a45129829643b55c90c061bb1b30d0a867202476438a7c243f46be6
Timestamp: 1704420885 Timestamp [UCT]: 2024-01-05 02:14:45 Age [y:d:h:m:s]: 01:129:14:51:48
Block: 928375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353789 RingCT/type: yes/0
Extra: 01a740e2aa4a45129829643b55c90c061bb1b30d0a867202476438a7c243f46be602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a88b73a9a56c99663809f484cf1c807f453832f3d6f20c702adcfafc98abdb 0.600000000000 1386233 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": 928385, "vin": [ { "gen": { "height": 928375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a88b73a9a56c99663809f484cf1c807f453832f3d6f20c702adcfafc98abdb" } } ], "extra": [ 1, 167, 64, 226, 170, 74, 69, 18, 152, 41, 100, 59, 85, 201, 12, 6, 27, 177, 179, 13, 10, 134, 114, 2, 71, 100, 56, 167, 194, 67, 244, 107, 230, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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