← previous blocknext block →recent activity
Analyzing
Block #98,414,016
14 transactions · 14 stateful · 2026-08-23 07:01:57 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,414,016 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x04d7a1e4…b8f4
0x34b655…2a6f
2 touches
0 conflicts
0x2557abf8…2901
0x34b655…2a6f
2 touches
0 conflicts
0x2847f658…c5e0
0x34b655…2a6f
2 touches
0 conflicts
0x371cbdc6…a53d
0x34b655…2a6f
2 touches
0 conflicts
0x3a786feb…5910
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc0b9bd73c8…277f1c
Audit this contract →
← previous block·next block →recent activity