← previous blocknext block →recent activity
Analyzing
Block #91,432,284
12 transactions · 12 stateful · 2026-07-29 19:54:57 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,432,284 · 12 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
5w06w17w28w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf861f787…c064
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x19b4e3fd…3821
0x34b655…2a6f
4 touches
1 conflict
0x219c6953…c961
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3796ff96…4de6
0x34b655…2a6f
4 touches
1 conflict
0x44d24653…fa2f
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
1 conflict on slot 0xf861f78745…e6c064
Audit this contract →
← previous block·next block →recent activity