← previous blocknext block →recent activity
Analyzing
Block #98,100,963
23 transactions · 22 stateful · 2026-08-22 04:46:15 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,100,963 · 23 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
2w03w05w08w19w211w313w415w118w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0x60ce2df9…5a39
0x34b655…2a6f
6 touches
3 conflicts
0x66386b72…0993
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity