← previous blocknext block →recent activity
Analyzing
Block #98,275,748
21 transactions · 19 stateful · 2026-08-22 19:26:18 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,275,748 · 21 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
2w04w05w16w29w312w413w014w115w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40c6eb19…32bb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0xa2869417…b1cb
0x34b655…2a6f
6 touches
3 conflicts
0x0ba7b8b2…dff4
0x34b655…2a6f
4 touches
1 conflict
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x43a82efb…51c8
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 0x40c6eb1939…d432bb
Audit this contract →
← previous block·next block →recent activity