← previous blocknext block →recent activity
Analyzing
Block #90,789,945
11 transactions · 11 stateful · 2026-07-27 14:00:12 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,789,945 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1265475a…18e3
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xc8fb3c38…8c4e
0x34b655…2a6f
6 touches
3 conflicts
0x2974f5ee…d34f
0x34b655…2a6f
4 touches
1 conflict
0x4cada0a8…c209
0x34b655…2a6f
4 touches
1 conflict
0x4d094aeb…b8b1
0x34b655…2a6f
4 touches
1 conflict
0x5cebb016…c149
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity