← previous blocknext block →recent activity
Analyzing
Block #99,320,966
24 transactions · 24 stateful · 2026-08-26 11:48:12 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,320,966 · 24 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
1w02w03w14w15w06w17w29w310w411w517w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728dd961…8676
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ab4ae11…1069
0x34b655…2a6f
4 touches
1 conflict
0x52bf7934…8746
0x34b655…2a6f
4 touches
1 conflict
0x67814bdb…ff15
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
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 0x728dd96113…0c8676
Audit this contract →
← previous block·next block →recent activity