← previous blocknext block →recent activity
Analyzing
Block #90,820,140
14 transactions · 14 stateful · 2026-07-27 16:32:12 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,820,140 · 14 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
2w03w06w17w28w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc00b5d0f…ccd7
0x34b655…2a6f
6 touches
3 conflicts
0x5e03c37b…9df2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2089dcc1…8f89
0x34b655…2a6f
4 touches
1 conflict
0x2b27a48b…deb2
0x34b655…2a6f
4 touches
1 conflict
0x33967383…de4d
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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 0xc00b5d0f7f…dfccd7
Audit this contract →
← previous block·next block →recent activity