Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e69ab4a56405b536a1a67940efdbf5c73f91183b3b1a450c63bf41e0bd7e0d1

Tx prefix hash: 37d143f37c45213cb955a05e9b671dedc905c868727c4a5e82ba7c74de401ab3
Tx public key: 7d7ffccca4e688d293ef56d73133a57a34e0b2c5f91fb87d260dc33c9e816c7c
Timestamp: 1684988446 Timestamp [UCT]: 2023-05-25 04:20:46 Age [y:d:h:m:s]: 01:356:07:34:23
Block: 767549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515887 RingCT/type: yes/0
Extra: 017d7ffccca4e688d293ef56d73133a57a34e0b2c5f91fb87d260dc33c9e816c7c02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.757080729000 dcy

stealth address amount amount idx
00: b580d99fa34d16dbd2ba805ad05cfd869bf30da890486ab3d2aaf199a7754f75 1.757080729000 1216674 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": 767559, "vin": [ { "gen": { "height": 767549 } } ], "vout": [ { "amount": 1757080729, "target": { "key": "b580d99fa34d16dbd2ba805ad05cfd869bf30da890486ab3d2aaf199a7754f75" } } ], "extra": [ 1, 125, 127, 252, 204, 164, 230, 136, 210, 147, 239, 86, 215, 49, 51, 165, 122, 52, 224, 178, 197, 249, 31, 184, 125, 38, 13, 195, 60, 158, 129, 108, 124, 2, 17, 0, 0, 0, 2, 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