← previous blocknext block →recent activity
Analyzing
Block #99,615,231
22 transactions · 22 stateful · 2026-08-27 12:35:37 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,615,231 · 22 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
2w03w16w08w09w010w111w012w016w117w118w119w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x1ec36a04…54bc
0x34b655…2a6f
4 touches
1 conflict
0x63016070…64d5
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0xb7c781c3…c3dc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity