← previous blocknext block →recent activity
Analyzing
Block #93,933,611
35 transactions · 23 stateful · 2026-08-07 13:37:54 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,933,611 · 35 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
1w08w19w212w013w215w220w021w027w328w129w233w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0x46e558af…7871
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
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 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity