← previous blocknext block →recent activity
Analyzing
Block #90,484,399
9 transactions · 9 stateful · 2026-07-26 12:23:08 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,484,399 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6c31fc…f4c3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x212c5b04…5f01
0x34b655…2a6f
2 touches
0 conflicts
0x277e1123…149d
0x34b655…2a6f
2 touches
0 conflicts
0x53355553…2976
0x34b655…2a6f
2 touches
0 conflicts
0x64687417…8d60
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
1 conflict on slot 0x0a6c31fc62…62f4c3
Audit this contract →
← previous block·next block →recent activity