← previous blocknext block →recent activity
Analyzing
Block #98,261,187
15 transactions · 15 stateful · 2026-08-22 18:13:03 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,261,187 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w19w211w312w413w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x09e0690d…6e3d
0xe52b14…7230
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
0x693b762e…1fcd
0xe52b14…7230
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
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity