← previous blocknext block →recent activity
Analyzing
Block #89,543,100
17 transactions · 16 stateful · 2026-07-23 01:56:04 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,543,100 · 17 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
2w03w15w26w37w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba059816…a847
0x34b655…2a6f
6 touches
3 conflicts
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x5b2c11f6…adbb
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4b
0x34b655…2a6f
4 touches
1 conflict
0x6630eed4…0b8c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xba0598166c…b0a847
Audit this contract →
← previous block·next block →recent activity