← previous blocknext block →recent activity
Analyzing
Block #99,616,002
21 transactions · 21 stateful · 2026-08-27 12:39:44 UTC
Parallelism
62/100
Blocked
48%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,616,002 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w08w110w211w312w213w315w416w517w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x8784f440…d92f
0x34b655…2a6f
10 touches
10 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0x30ae635d…5e67
0x34b655…2a6f
6 touches
3 conflicts
0xea1fc966…1676
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity