← previous blocknext block →recent activity
Analyzing
Block #98,068,696
9 transactions · 8 stateful · 2026-08-22 02:03:52 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,068,696 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xdeaa385f…6b8b
0x34b655…2a6f
4 touches
1 conflict
0x0e876f1e…3f0a
0x34b655…2a6f
2 touches
0 conflicts
0x15073066…40a5
0x34b655…2a6f
2 touches
0 conflicts
0x166e9860…6947
0x34b655…2a6f
2 touches
0 conflicts
0x29571880…30e5
0x34b655…2a6f
2 touches
0 conflicts
0x3aed8a17…20f9
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 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity