← previous blocknext block →recent activity
Analyzing
Block #94,751,747
16 transactions · 14 stateful · 2026-08-10 10:30:02 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,751,747 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca713a22…3083
0x34b655…2a6f
4 touches
1 conflict
0xcd84df4a…6dc8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x13c2a20d…2c6d
0x34b655…2a6f
4 touches
1 conflict
0x52f3d91c…1822
0x34b655…2a6f
4 touches
1 conflict
0x56b75a1a…340c
0x34b655…2a6f
4 touches
1 conflict
0x65713190…c3d3
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xca713a22d6…9a3083
Audit this contract →
← previous block·next block →recent activity