← previous blocknext block →recent activity
Analyzing
Block #99,505,137
14 transactions · 11 stateful · 2026-08-27 03:15:36 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,505,137 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x092a277d…420c
0x34b655…2a6f
6 touches
3 conflicts
0x51215051…bbbc
0x34b655…2a6f
6 touches
3 conflicts
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0x87ec4b40…c550
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xae62d2a9…84dd
0x34b655…2a6f
4 touches
1 conflict
0xb450d6cf…be0b
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity