← previous blocknext block →recent activity
Analyzing
Block #98,272,451
17 transactions · 16 stateful · 2026-08-22 19:09:42 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,272,451 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w19w210w311w412w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf00bcd…2019
0x34b655…2a6f
8 touches
6 conflicts
0x523b8cf5…0ac7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x50732b88…8402
0x34b655…2a6f
4 touches
1 conflict
0xa38c430a…e3cb
0x34b655…2a6f
4 touches
1 conflict
0xaf30c163…0fb6
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xfaf00bcd33…4a2019
Audit this contract →
← previous block·next block →recent activity