← previous blocknext block →recent activity
Analyzing
Block #99,163,868
22 transactions · 21 stateful · 2026-08-25 22:37:48 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,163,868 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w111w013w114w015w116w218w219w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd9f30bc9…8529
0x34b655…2a6f
6 touches
3 conflicts
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
4 touches
1 conflict
0x388d69c4…4288
0x188d58…ea8e
4 touches
1 conflict
0xa5a4bb2c…f2c7
0x188d58…ea8e
4 touches
1 conflict
0xd9a7cef1…1ed5
0x188d58…ea8e
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity