← previous blocknext block →recent activity
Analyzing
Block #93,408,200
22 transactions · 19 stateful · 2026-08-05 17:36:04 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,408,200 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w08w19w110w011w212w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0x0606febb…c587
0x34b655…2a6f
4 touches
1 conflict
0x17d94c79…2463
0x34b655…2a6f
4 touches
1 conflict
0x1c3c9acb…e2b0
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x1db9ae71…2888
0x34b655…2a6f
4 touches
1 conflict
0x27680977…85ae
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
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
3 conflicts on slot 0x428b6e5b99…c18909
Audit this contract →
← previous block·next block →recent activity