← previous blocknext block →recent activity
Analyzing
Block #98,415,769
9 transactions · 7 stateful · 2026-08-23 07:10:46 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,415,769 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x9366c0d5…0d9f
0x34b655…2a6f
4 touches
1 conflict
0xde639eb7…c040
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9284
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9286
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9287
0x2b46c0…1669
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity