← previous blocknext block →recent activity
Analyzing
Block #99,872,116
15 transactions · 15 stateful · 2026-08-28 10:16:00 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,872,116 · 15 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
2w03w14w25w07w18w29w311w413w014w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x470b41f6…fc68
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xdb780694…a2f0
0x34b655…2a6f
6 touches
3 conflicts
0xfc29df43…6760
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x91cdfdeb…7feb
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
10 conflicts on slot 0x470b41f691…2dfc68
Audit this contract →
← previous block·next block →recent activity