← previous blocknext block →recent activity
Analyzing
Block #99,316,436
10 transactions · 10 stateful · 2026-08-26 11:25:25 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,316,436 · 10 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
2w03w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2c4f30a9…b162
0x065c9d…c394
4 touches
1 conflict
0xb58c99bb…d1df
0x065c9d…c394
3 touches
1 conflict
0x62fcaafd…710c
0x065c9d…c394
3 touches
1 conflict
0xa48ec3ec…7a74
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x1f5a2e2b…65f1
0x2b46c0…1669
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity