← previous blocknext block →recent activity
Analyzing
Block #99,958,177
14 transactions · 14 stateful · 2026-08-28 17:29:43 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,958,177 · 14 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
5w06w17w28w39w111w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2288c7e7…982a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfc2493d3…6898
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
6 touches
3 conflicts
0x3f1bf3a4…c32c
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x42d0f569…5f4b
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
15 conflicts on slot 0x2288c7e7b1…41982a
Audit this contract →
← previous block·next block →recent activity