← previous blocknext block →recent activity
Analyzing
Block #98,458,052
23 transactions · 23 stateful · 2026-08-23 10:43:41 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,458,052 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w210w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…153c
0x34b655…2a6f
6 touches
3 conflicts
0xea8b3cfe…e6d4
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153b
0x34b655…2a6f
6 touches
3 conflicts
0x7a1531cd…7319
0x34b655…2a6f
6 touches
3 conflicts
0x5db20ed9…9d47
0x34b655…2a6f
6 touches
3 conflicts
0x0aee38d8…ae3d
0x34b655…2a6f
5 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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity