← previous blocknext block →recent activity
Analyzing
Block #98,915,256
17 transactions · 16 stateful · 2026-08-25 01:40:16 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,915,256 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0203a60f…d0bd
0x34b655…2a6f
2 touches
0 conflicts
0x0baf5ede…b815
0x34b655…2a6f
2 touches
0 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
2 touches
0 conflicts
0x12e605da…9ca3
0x34b655…2a6f
2 touches
0 conflicts
0x12e77486…ec2b
0x34b655…2a6f
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
1 conflict on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity