← previous blocknext block →recent activity
Analyzing
Block #91,242,299
11 transactions · 11 stateful · 2026-07-29 03:56:51 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,242,299 · 11 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
3w04w16w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0140fbd3…d957
0x34b655…2a6f
4 touches
1 conflict
0x395c6b2e…fed1
0x34b655…2a6f
4 touches
1 conflict
0x55aae70f…b97a
0x34b655…2a6f
4 touches
1 conflict
0x617a8bb8…2b5c
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
1 conflict on slot 0x0140fbd33f…b8d957
Audit this contract →
← previous block·next block →recent activity