← previous blocknext block →recent activity
Analyzing
Block #99,478,371
24 transactions · 19 stateful · 2026-08-27 01:00:48 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,478,371 · 24 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
1w02w17w08w113w214w315w416w517w418w020w122w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xad98bb8e…f3bc
0x34b655…2a6f
6 touches
3 conflicts
0x41f621e0…9e98
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
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 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity