← previous blocknext block →recent activity
Analyzing
Block #98,456,461
20 transactions · 17 stateful · 2026-08-23 10:35:40 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,456,461 · 20 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
1w04w16w07w110w211w312w413w418w019w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8f84702c…c5f9
0x34b655…2a6f
8 touches
6 conflicts
0x9cb6ce8f…87bb
0x34b655…2a6f
6 touches
3 conflicts
0x840b9ed3…5a3e
0x34b655…2a6f
6 touches
3 conflicts
0x4c20d376…0819
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity