← previous blocknext block →recent activity
Analyzing
Block #90,610,938
12 transactions · 12 stateful · 2026-07-26 22:59:39 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,610,938 · 12 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
5w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf9501a0…022b
0x34b655…2a6f
4 touches
1 conflict
0xb7fb66e8…4f94
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xdc972bba…e133
0xe52b14…7230
3 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x3eede796…d745
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0xbf9501a09d…a0022b
Audit this contract →
← previous block·next block →recent activity