← previous blocknext block →recent activity
Analyzing
Block #98,737,132
26 transactions · 18 stateful · 2026-08-24 10:43:48 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,737,132 · 26 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
1w05w16w014w016w117w218w219w121w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0x468a6f01…fbc0
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x38963aeb…c33f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa019dd86…b976
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 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity