← previous blocknext block →recent activity
Analyzing
Block #99,254,391
17 transactions · 17 stateful · 2026-08-26 06:13:14 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,254,391 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w18w211w112w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbbc93dd8…7766
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xc2aacf41…5500
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity