Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64531bd2ccdcd2ae8d4a5f2f2c929c1cf93a18a1231230469636a18d1f28ec7

Tx prefix hash: 3b057c0cdd8a5f86d7d020a575d130f37392d2b13f2dc00828ad05a53c813eb7
Tx public key: a2e1130406252e035236ec7f8e8475b33c005fefe3472bc6b466644034d4c3d0
Timestamp: 1725097859 Timestamp [UCT]: 2024-08-31 09:50:59 Age [y:d:h:m:s]: 00:290:16:17:34
Block: 1099824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207526 RingCT/type: yes/0
Extra: 01a2e1130406252e035236ec7f8e8475b33c005fefe3472bc6b466644034d4c3d0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25793368b00386dd409e7d3df3857221547adde38e7697e323cc6782f052bc7f 0.600000000000 1575793 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": 1099834, "vin": [ { "gen": { "height": 1099824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25793368b00386dd409e7d3df3857221547adde38e7697e323cc6782f052bc7f" } } ], "extra": [ 1, 162, 225, 19, 4, 6, 37, 46, 3, 82, 54, 236, 127, 142, 132, 117, 179, 60, 0, 95, 239, 227, 71, 43, 198, 180, 102, 100, 64, 52, 212, 195, 208, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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