← previous blocknext block →recent activity
Analyzing
Block #98,425,416
21 transactions · 20 stateful · 2026-08-23 07:59:19 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,425,416 · 21 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
1w03w04w15w16w212w213w314w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24364d4e…c6e1
0x34b655…2a6f
12 touches
15 conflicts
0x8590c11e…2f05
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x58799a46…7030
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2e74ccf…8a8a
0x34b655…2a6f
6 touches
3 conflicts
0x91f10590…5d13
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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 0x24364d4e4c…38c6e1
Audit this contract →
← previous block·next block →recent activity