← previous blocknext block →recent activity
Analyzing
Block #96,157,839
17 transactions · 15 stateful · 2026-08-15 08:38:41 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,157,839 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w410w511w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x1f40ac22…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
6 touches
3 conflicts
0xaba6578d…bd48
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xffc26b06…715e
0x34b655…2a6f
4 touches
1 conflict
0x43a02937…4672
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
15 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity