← previous blocknext block →recent activity
Analyzing
Block #98,286,723
25 transactions · 20 stateful · 2026-08-22 20:21:30 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,286,723 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w210w316w417w518w624w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x1408e7c7…f324
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xe0a62266…06f4
0x34b655…2a6f
6 touches
3 conflicts
0x5581159e…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0x58737d82…26ba
0x34b655…2a6f
6 touches
3 conflicts
0x5f134e28…babf
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity