Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 838dcd7517ba5fcf8d1924b219d5a5132086843f4210446aab24253687728d6c

Tx prefix hash: a84bd58dd4650c4db46322eb832d1762391302a7218398d80230797b5923fc88
Tx public key: e6a77d97a6aebfb3567b6f73beaa5576fdf4a5839196b3e6de6814fdd5a261dd
Timestamp: 1733832693 Timestamp [UCT]: 2024-12-10 12:11:33 Age [y:d:h:m:s]: 00:113:10:17:52
Block: 1172140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80843 RingCT/type: yes/0
Extra: 01e6a77d97a6aebfb3567b6f73beaa5576fdf4a5839196b3e6de6814fdd5a261dd021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 533e17c388d5844e5b543ffde3c935bd966b122c23893f03718df7d3f672975f 0.600000000000 1657993 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": 1172150, "vin": [ { "gen": { "height": 1172140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533e17c388d5844e5b543ffde3c935bd966b122c23893f03718df7d3f672975f" } } ], "extra": [ 1, 230, 167, 125, 151, 166, 174, 191, 179, 86, 123, 111, 115, 190, 170, 85, 118, 253, 244, 165, 131, 145, 150, 179, 230, 222, 104, 20, 253, 213, 162, 97, 221, 2, 17, 0, 0, 0, 8, 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