← previous blocknext block →recent activity
Analyzing
Block #93,309,884
16 transactions · 15 stateful · 2026-08-05 09:21:46 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,309,884 · 16 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
3w04w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x1635499f…47cb
0x34b655…2a6f
4 touches
1 conflict
0x97e42545…c316
0x34b655…2a6f
3 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
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 0x4e8c4408ae…50d37a
Audit this contract →
← previous block·next block →recent activity