← previous blocknext block →recent activity
Analyzing
Block #98,263,329
26 transactions · 24 stateful · 2026-08-22 18:23:49 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,263,329 · 26 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
1w02w03w14w06w18w09w111w012w113w016w017w118w119w220w323w224w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x09d42313…244d
0x34b655…2a6f
6 touches
3 conflicts
0x057c6242…da7e
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0x68297b76…8e24
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity