← previous blocknext block →recent activity
Analyzing
Block #91,982,920
17 transactions · 16 stateful · 2026-07-31 18:05:01 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,982,920 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w28w19w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
6 touches
3 conflicts
0x33649c4f…b327
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x98fb5d04…b545
0x34b655…2a6f
4 touches
1 conflict
0x9efbd42c…c1bb
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity