← previous blocknext block →recent activity
Analyzing
Block #99,185,018
14 transactions · 14 stateful · 2026-08-26 00:24:11 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,185,018 · 14 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
2w03w16w07w29w110w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb32e068b…6e1a
0x34b655…2a6f
6 touches
3 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
4 touches
1 conflict
0x44e65225…eb2e
0x34b655…2a6f
4 touches
1 conflict
0x4be08494…a1ab
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0xb32e068b05…db6e1a
Audit this contract →
← previous block·next block →recent activity