← previous blocknext block →recent activity
Analyzing
Block #99,330,172
15 transactions · 14 stateful · 2026-08-26 12:34:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,330,172 · 15 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
3w04w15w26w311w313w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x18017399…84f4
0x34b655…2a6f
6 touches
3 conflicts
0xa7cf7ad1…f6f8
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6fc2788e…3927
0x34b655…2a6f
4 touches
1 conflict
0x962713d6…7374
0x34b655…2a6f
4 touches
1 conflict
0xa70cb615…11da
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity