← previous blocknext block →recent activity
Analyzing
Block #99,100,463
29 transactions · 28 stateful · 2026-08-25 17:18:43 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,100,463 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w213w315w016w417w122w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4b2a427…0234
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x71f739c7…4879
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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 0xf4b2a42760…660234
Audit this contract →
← previous block·next block →recent activity