← previous blocknext block →recent activity
Analyzing
Block #90,537,192
17 transactions · 17 stateful · 2026-07-26 16:48:40 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,537,192 · 17 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
4w05w16w27w08w39w113w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbb4fd99a…afa6
0x34b655…2a6f
6 touches
3 conflicts
0xa24365bc…5064
0x34b655…2a6f
6 touches
3 conflicts
0x57330c5d…9973
0x34b655…2a6f
6 touches
3 conflicts
0x45d3434f…6c0c
0x34b655…2a6f
6 touches
3 conflicts
0xdfa9b704…9d46
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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity