← previous blocknext block →recent activity
Analyzing
Block #91,072,414
24 transactions · 22 stateful · 2026-07-28 13:42:10 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,072,414 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w012w115w119w220w321w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x636b8021…5bef
0x34b655…2a6f
4 touches
1 conflict
0x67459137…de7e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity