← previous blocknext block →recent activity
Analyzing
Block #98,101,654
21 transactions · 20 stateful · 2026-08-22 04:49:43 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,101,654 · 21 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
2w03w04w06w07w18w214w115w016w117w219w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xcf11cf1a…ec04
0x34b655…2a6f
6 touches
3 conflicts
0xadbda1a7…5f21
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x5a855481…c75b
0x34b655…2a6f
4 touches
1 conflict
0x614427d2…e7c2
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
3 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity