← previous blocknext block →recent activity
Analyzing
Block #90,991,393
8 transactions · 8 stateful · 2026-07-28 06:53:47 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,991,393 · 8 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x124a2fe8…2ea9
0x34b655…2a6f
4 touches
1 conflict
0x48965dfe…432b
0x34b655…2a6f
4 touches
1 conflict
0x72ed31c7…de4d
0x34b655…2a6f
4 touches
1 conflict
0x05fc3be3…9516
0x34b655…2a6f
2 touches
0 conflicts
0x0cd3cc12…6efa
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x20f13ae0…cca8
0x34b655…2a6f
2 touches
0 conflicts
0x20f1b9d2…bf33
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 0x124a2fe822…4a2ea9
Audit this contract →
← previous block·next block →recent activity