← previous blocknext block →recent activity
Analyzing
Block #90,879,496
7 transactions · 7 stateful · 2026-07-27 21:30:49 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,879,496 · 7 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ea25e92…a36d
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xb1a69eee…97a5
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0xb027a20d…5efe
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xcd6a810f…561e
0x34b655…2a6f
4 touches
1 conflict
0xff3dbbcd…5060
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 0x3ea25e9273…d9a36d
Audit this contract →
← previous block·next block →recent activity