← previous blocknext block →recent activity
Analyzing
Block #91,064,782
16 transactions · 14 stateful · 2026-07-28 13:03:47 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,064,782 · 16 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
4w05w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9cbb059…9e23
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x1e0018c3…e6a7
0x34b655…2a6f
2 touches
0 conflicts
0x2c7064fa…682d
0x34b655…2a6f
2 touches
0 conflicts
0x2d6abdbe…1c2e
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
0x34b655…2a6f
2 touches
0 conflicts
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 0xc9cbb059e2…659e23
Audit this contract →
← previous block·next block →recent activity