← previous blocknext block →recent activity
Analyzing
Block #98,066,839
21 transactions · 20 stateful · 2026-08-22 01:54:31 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,066,839 · 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
1w02w03w04w16w19w010w111w013w218w219w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x0e5786aa…8aed
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x299c0f04…09cf
0x34b655…2a6f
4 touches
1 conflict
0x2c271701…fb3e
0x34b655…2a6f
4 touches
1 conflict
0x4635fb46…4cfd
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity