← previous blocknext block →recent activity
Analyzing
Block #99,483,008
21 transactions · 17 stateful · 2026-08-27 01:24:12 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,483,008 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w09w110w212w313w414w517w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7684f61e…fc67
0x34b655…2a6f
10 touches
10 conflicts
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf343a91e…e362
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
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
10 conflicts on slot 0x7684f61ea9…6ffc67
Audit this contract →
← previous block·next block →recent activity