Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a4d6fb334bf167f2c6a742ccdf010473ba2b1e92bf574062ee2891616a216e

Tx prefix hash: 011414105d82be505502e76013e027f61c95826110b14ecd911d6a978c84e939
Tx public key: bf504e07dab75b3d8c8646c1a9fa3533fb28361503edca5f62a445a4d410e4dc
Timestamp: 1732271770 Timestamp [UCT]: 2024-11-22 10:36:10 Age [y:d:h:m:s]: 00:001:16:35:06
Block: 1159198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1211 RingCT/type: yes/0
Extra: 01bf504e07dab75b3d8c8646c1a9fa3533fb28361503edca5f62a445a4d410e4dc021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46344f318f155506aed70ddbf01b08834d94ac80753d24080ca516cf71e80094 0.600000000000 1644831 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": 1159208, "vin": [ { "gen": { "height": 1159198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46344f318f155506aed70ddbf01b08834d94ac80753d24080ca516cf71e80094" } } ], "extra": [ 1, 191, 80, 78, 7, 218, 183, 91, 61, 140, 134, 70, 193, 169, 250, 53, 51, 251, 40, 54, 21, 3, 237, 202, 95, 98, 164, 69, 164, 212, 16, 228, 220, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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