← previous blocknext block →recent activity
Analyzing
Block #99,362,727
37 transactions · 34 stateful · 2026-08-26 15:18:28 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
1.49
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,362,727 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w18w19w011w113w114w215w016w317w118w223w325w428w229w535w136w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x02373c43…3cb3
0x34b655…2a6f
10 touches
10 conflicts
0x9513aafb…bb7f
0x34b655…2a6f
10 touches
10 conflicts
0xd97b0449…00a0
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x17ff2059…ddb4
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity