← previous blocknext block →recent activity
Analyzing
Block #90,706,967
13 transactions · 11 stateful · 2026-07-27 07:02:44 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,706,967 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7a916b05…8a00
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xfc3a3e66…1681
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0x033156c1…b94e
0x34b655…2a6f
2 touches
0 conflicts
0x05faf685…a62b
0x34b655…2a6f
2 touches
0 conflicts
0x14638472…934f
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity