← previous blocknext block →recent activity
Analyzing
Block #99,956,910
19 transactions · 19 stateful · 2026-08-28 17:23:20 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,956,910 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w16w27w310w411w512w616w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3aa2022…9e09
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5ebbb68b…5d78
0x34b655…2a6f
6 touches
3 conflicts
0x732ef63b…29c6
0x34b655…2a6f
6 touches
3 conflicts
0xeec73967…cccf
0x34b655…2a6f
6 touches
3 conflicts
0x65cd82b5…e7d4
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
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
21 conflicts on slot 0xb3aa2022cd…dd9e09
Audit this contract →
← previous block·next block →recent activity