Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31432e41747b5bc5f2918134460a9f1f4696a3dcaec7ff466d5b6f8ec0020bc6

Tx prefix hash: 82811d6faddb588bb36b95bd41fe13dab94b4e4b3e902ae99641cc14da0d95a0
Tx public key: 21892082aa3386179e5f4f0d83d66c25be7582c7d72f07121a0efe8a97be7fe4
Timestamp: 1735560947 Timestamp [UCT]: 2024-12-30 12:15:47 Age [y:d:h:m:s]: 00:088:07:08:12
Block: 1186435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62889 RingCT/type: yes/0
Extra: 0121892082aa3386179e5f4f0d83d66c25be7582c7d72f07121a0efe8a97be7fe4021100000015007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3e3dd8f397f941bc13c575936ab452824c138a90ea287132beb2671f49f414 0.600000000000 1672916 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": 1186445, "vin": [ { "gen": { "height": 1186435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3e3dd8f397f941bc13c575936ab452824c138a90ea287132beb2671f49f414" } } ], "extra": [ 1, 33, 137, 32, 130, 170, 51, 134, 23, 158, 95, 79, 13, 131, 214, 108, 37, 190, 117, 130, 199, 215, 47, 7, 18, 26, 14, 254, 138, 151, 190, 127, 228, 2, 17, 0, 0, 0, 21, 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