← previous blocknext block →recent activity
Analyzing
Block #98,482,134
11 transactions · 11 stateful · 2026-08-23 12:45:02 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,482,134 · 11 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
1w08w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x462523b6…1a4a
0x34b655…2a6f
4 touches
1 conflict
0xe1fc046b…9af3
0x34b655…2a6f
3 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity