← previous blocknext block →recent activity
Analyzing
Block #99,183,851
24 transactions · 21 stateful · 2026-08-26 00:18:19 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,183,851 · 24 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
1w02w03w14w26w17w28w010w111w214w215w317w120w321w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0781f8af…cdd9
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x8311570f…5321
0x34b655…2a6f
8 touches
6 conflicts
0xb157841c…54c2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
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 0x0781f8af16…3ecdd9
Audit this contract →
← previous block·next block →recent activity