← previous blocknext block →recent activity
Analyzing
Block #99,619,074
19 transactions · 16 stateful · 2026-08-27 12:55:31 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,619,074 · 19 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
1w02w13w04w15w26w37w313w414w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd542fff1…1df2
0x34b655…2a6f
4 touches
1 conflict
0xe0f57943…818d
0x34b655…2a6f
4 touches
1 conflict
0xb91a987e…2365
0x34b655…2a6f
4 touches
1 conflict
0x4f8043ce…269c
0x34b655…2a6f
4 touches
1 conflict
0x23c1dd54…8fdf
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity