← previous blocknext block →recent activity
Analyzing
Block #99,954,061
23 transactions · 21 stateful · 2026-08-28 17:08:59 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,954,061 · 23 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
1w02w15w16w07w18w29w010w113w214w316w417w018w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x615dda76…358f
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x615dda76c4…ca358f
Audit this contract →
← previous block·next block →recent activity