← previous blocknext block →recent activity
Analyzing
Block #98,596,596
26 transactions · 23 stateful · 2026-08-23 22:39:10 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,596,596 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w18w115w217w018w120w321w422w123w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xc8ab31f9…8ce9
0xa6afd3…d132
6 touches
3 conflicts
0x279ddfdc…78fb
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity