← previous blocknext block →recent activity
Analyzing
Block #98,527,670
16 transactions · 14 stateful · 2026-08-23 16:39:38 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,527,670 · 16 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
2w05w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xcd1306ad…f1b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0abd58f2…77a4
0x34b655…2a6f
2 touches
0 conflicts
0x0ddf8d9a…405f
0x34b655…2a6f
2 touches
0 conflicts
0x2beef0db…072d
0x34b655…2a6f
2 touches
0 conflicts
0x4d6cf1f2…26f8
0x34b655…2a6f
2 touches
0 conflicts
0x5fde4971…aac9
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 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity