← previous blocknext block →recent activity
Analyzing
Block #90,448,143
13 transactions · 13 stateful · 2026-07-26 09:20:42 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,448,143 · 13 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec501e17…45fd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x7c7eff13…16db
0x34b655…2a6f
2 touches
0 conflicts
0x86f32276…0ebf
0x34b655…2a6f
2 touches
0 conflicts
0x94710b77…a921
0x34b655…2a6f
2 touches
0 conflicts
0xc2db6e7a…d074
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 0xec501e1764…5245fd
Audit this contract →
← previous block·next block →recent activity