← previous blocknext block →recent activity
Analyzing
Block #98,491,408
41 transactions · 29 stateful · 2026-08-23 13:31:41 UTC
Parallelism
88/100
Blocked
34%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,491,408 · 41 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
9w010w011w116w017w119w226w028w129w232w334w337w038w139w240w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3580964…aa6b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x261cbea7…e35d
0x34b655…2a6f
8 touches
6 conflicts
0x27e94395…baa0
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5222901c…d3d2
0x34b655…2a6f
6 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 0xb35809645e…8caa6b
Audit this contract →
← previous block·next block →recent activity