← previous blocknext block →recent activity
Analyzing
Block #90,289,934
8 transactions · 8 stateful · 2026-07-25 19:51:08 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,289,934 · 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
2w03w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x27e8e7c5…92eb
0x34b655…2a6f
4 touches
1 conflict
0x2a5e2b11…1c2b
0x34b655…2a6f
4 touches
1 conflict
0x47b56a32…dcf4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f357fc9…778e
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity