Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df35df42a611650e448e22d13b04bdf2dd078ed76c804faf52cf861b68509409

Tx prefix hash: bae7a6cbfdc05d937fbaee3d781b86527ca665d123290de1d032a3777243e486
Tx public key: a9f7a9a20aa1cfa9b3888a6fce67151a6867fe7bf4a84433991ee2c231563dec
Timestamp: 1722481727 Timestamp [UCT]: 2024-08-01 03:08:47 Age [y:d:h:m:s]: 00:252:17:57:49
Block: 1078128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180540 RingCT/type: yes/0
Extra: 01a9f7a9a20aa1cfa9b3888a6fce67151a6867fe7bf4a84433991ee2c231563dec021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e6732a7b45ca4e0fcfe4eeb96874a57ba1425096c72bb6ad58d3441d635630 0.600000000000 1550691 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": 1078138, "vin": [ { "gen": { "height": 1078128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e6732a7b45ca4e0fcfe4eeb96874a57ba1425096c72bb6ad58d3441d635630" } } ], "extra": [ 1, 169, 247, 169, 162, 10, 161, 207, 169, 179, 136, 138, 111, 206, 103, 21, 26, 104, 103, 254, 123, 244, 168, 68, 51, 153, 30, 226, 194, 49, 86, 61, 236, 2, 17, 0, 0, 0, 19, 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