Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d64eccb62b45aed647746281c6213d5772bc8c81ec810afd0394489a00e1e90

Tx prefix hash: b1574d1c80b164dfd9cede782852a7e16356ee95ae4e8772017ebeb10d46b5b8
Tx public key: b2f1b7b4c57270d26e38cec0a47baf89d1536f71c7128f0a2709d5bde02df7ca
Timestamp: 1747972900 Timestamp [UCT]: 2025-05-23 04:01:40 Age [y:d:h:m:s]: 00:181:21:32:13
Block: 1288929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127687 RingCT/type: yes/0
Extra: 01b2f1b7b4c57270d26e38cec0a47baf89d1536f71c7128f0a2709d5bde02df7ca0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcc3c46d1d989bfecfeb3233914620fd9bbf764413acfad2b0423565c99dd966 0.600000000000 1776396 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": 1288939, "vin": [ { "gen": { "height": 1288929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcc3c46d1d989bfecfeb3233914620fd9bbf764413acfad2b0423565c99dd966" } } ], "extra": [ 1, 178, 241, 183, 180, 197, 114, 112, 210, 110, 56, 206, 192, 164, 123, 175, 137, 209, 83, 111, 113, 199, 18, 143, 10, 39, 9, 213, 189, 224, 45, 247, 202, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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