← previous blocknext block →recent activity
Analyzing
Block #98,101,755
29 transactions · 23 stateful · 2026-08-22 04:50:14 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,101,755 · 29 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w07w08w110w011w113w114w219w220w021w123w026w127w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3836a730…b3a9
0x34b655…2a6f
4 touches
1 conflict
0x40d84fed…3d92
0x34b655…2a6f
4 touches
1 conflict
0x53eac009…b61b
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity