Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a4f5c30ce5e23406fb75492a52f0816720fa5c4d9debf29f28878c1992d2d4

Tx prefix hash: ea298372ae11f391c325d147982d3b62f2ec8f5656263c75ffb23432ed43f0a9
Tx public key: 0b7b069b4071678df16510cd2e6c23be58163519cfad97e39077a6375a8f15a9
Timestamp: 1739265404 Timestamp [UCT]: 2025-02-11 09:16:44 Age [y:d:h:m:s]: 00:238:22:30:35
Block: 1216836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168467 RingCT/type: yes/0
Extra: 010b7b069b4071678df16510cd2e6c23be58163519cfad97e39077a6375a8f15a9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699a780369a5c44d2624c3b2eb53c74f16e754cdb6b92c193210ec4c807e2df3 0.600000000000 1703643 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": 1216846, "vin": [ { "gen": { "height": 1216836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699a780369a5c44d2624c3b2eb53c74f16e754cdb6b92c193210ec4c807e2df3" } } ], "extra": [ 1, 11, 123, 6, 155, 64, 113, 103, 141, 241, 101, 16, 205, 46, 108, 35, 190, 88, 22, 53, 25, 207, 173, 151, 227, 144, 119, 166, 55, 90, 143, 21, 169, 2, 17, 0, 0, 0, 4, 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