← previous blocknext block →recent activity
Analyzing
Block #90,437,713
16 transactions · 16 stateful · 2026-07-26 08:27:42 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,437,713 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w49w110w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xfece6a0e…3030
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x94b46bd0…e95d
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0a906ba5…2454
0x34b655…2a6f
4 touches
1 conflict
0x3d15edcb…8ef6
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity