← previous blocknext block →recent activity
Analyzing
Block #91,009,673
8 transactions · 7 stateful · 2026-07-28 08:26:24 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,009,673 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff533a5f…685e
0x34b655…2a6f
4 touches
1 conflict
0x10af5537…5a9a
0x34b655…2a6f
4 touches
1 conflict
0x27d74e37…a5b9
0x34b655…2a6f
4 touches
1 conflict
0x2bcdd4a1…3d3a
0x34b655…2a6f
4 touches
1 conflict
0x3377da70…01e5
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x4efc6a2c…2f6c
0x34b655…2a6f
4 touches
1 conflict
0x5fee36ab…1014
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 0xff533a5f3e…e5685e
Audit this contract →
← previous block·next block →recent activity