← previous blocknext block →recent activity
Analyzing
Block #99,156,362
21 transactions · 18 stateful · 2026-08-25 22:00:02 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,156,362 · 21 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
3w04w18w19w110w215w016w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd97b0449…00a0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf1827be6…8c24
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x79355527…f5c4
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
1 conflict on slot 0xd97b04496e…0c00a0
Audit this contract →
← previous block·next block →recent activity