← previous blocknext block →recent activity
Analyzing
Block #93,063,382
11 transactions · 10 stateful · 2026-08-04 12:41:03 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,063,382 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3accf018…2e8b
0x34b655…2a6f
4 touches
1 conflict
0xa3791570…f07a
0x34b655…2a6f
4 touches
1 conflict
0x3d8ce53e…1aee
0x065c9d…c394
2 touches
0 conflicts
0x6321cc3f…fcb3
0x065c9d…c394
2 touches
0 conflicts
0xc8a64123…2e72
0x065c9d…c394
2 touches
0 conflicts
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity