← previous blocknext block →recent activity
Analyzing
Block #90,462,039
13 transactions · 12 stateful · 2026-07-26 10:30:35 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,462,039 · 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
1w02w14w05w07w18w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b9df115…12d9
0x34b655…2a6f
4 touches
1 conflict
0xa1f57fdd…f521
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc44bc18…e1e4
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1f81743e…117b
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
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
1 conflict on slot 0x8b9df1155e…be12d9
Audit this contract →
← previous block·next block →recent activity