← previous blocknext block →recent activity
Analyzing
Block #90,976,379
20 transactions · 20 stateful · 2026-07-28 05:38:11 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,976,379 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w111w214w315w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x8641bdc9…7e57
0x34b655…2a6f
4 touches
1 conflict
0x96562bca…f07c
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xa49449e1…3460
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
6 conflicts on slot 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity