← previous blocknext block →recent activity
Analyzing
Block #99,493,054
16 transactions · 13 stateful · 2026-08-27 02:14:46 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,493,054 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w210w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0x00b91c15…809d
0x34b655…2a6f
4 touches
1 conflict
0x26471102…35f9
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
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