← previous blocknext block →recent activity
Analyzing
Block #99,478,410
25 transactions · 22 stateful · 2026-08-27 01:00:59 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
2.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,478,410 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w17w28w311w414w515w616w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xf38a3927…ad62
0x34b655…2a6f
12 touches
15 conflicts
0xb4c0e531…0bb8
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6d8ad688…4bf5
0xa6afd3…d132
6 touches
3 conflicts
0x51215051…bbbc
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity