← previous blocknext block →recent activity
Analyzing
Block #99,780,817
34 transactions · 33 stateful · 2026-08-28 02:34:10 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,780,817 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w29w010w111w112w215w016w118w019w120w222w023w124w125w326w429w530w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
10 touches
10 conflicts
0x261cbea7…e35e
0x34b655…2a6f
10 touches
10 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x2faeb77a…58f6
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x399d9048…6ef9
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity