← previous blocknext block →recent activity
Analyzing
Block #98,001,050
35 transactions · 19 stateful · 2026-08-21 20:23:14 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,001,050 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w09w111w218w019w021w326w027w130w131w232w334w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbce65196…4c2a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba2c6d17…3c30
0x34b655…2a6f
5 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
5 touches
3 conflicts
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
6 conflicts on slot 0xe5e7089a63…bcfb91
Audit this contract →
← previous block·next block →recent activity