← previous blocknext block →recent activity
Analyzing
Block #90,978,152
9 transactions · 7 stateful · 2026-07-28 05:47:06 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,978,152 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x006c3b86…59a9
0x34b655…2a6f
6 touches
3 conflicts
0x32b5b2d6…fb21
0x34b655…2a6f
6 touches
3 conflicts
0x72ed31c7…de4d
0x34b655…2a6f
6 touches
3 conflicts
0x7ea5ce4b…1e5b
0x34b655…2a6f
6 touches
3 conflicts
0xa5908184…0fef
0x34b655…2a6f
6 touches
3 conflicts
0xc53843f7…3379
0x34b655…2a6f
6 touches
3 conflicts
0xd9a771df…a27b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity