← previous blocknext block →recent activity
Analyzing
Block #90,916,431
8 transactions · 8 stateful · 2026-07-28 00:36:39 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,916,431 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
2 touches
0 conflicts
0x2fade833…5de4
0x34b655…2a6f
2 touches
0 conflicts
0x32e2bb09…8b3a
0x34b655…2a6f
2 touches
0 conflicts
0x3c0c2f32…c3df
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity