← previous blocknext block →recent activity
Analyzing
Block #97,521,135
10 transactions · 9 stateful · 2026-08-20 03:41:29 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,521,135 · 10 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
1w03w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc158f1d9…bc17
0x34b655…2a6f
4 touches
1 conflict
0xca401ec1…58f8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x287f71b4…5a6a
0x34b655…2a6f
2 touches
0 conflicts
0x331a294a…7f59
0x34b655…2a6f
2 touches
0 conflicts
0x391d75c5…b826
0x34b655…2a6f
2 touches
0 conflicts
0x3d354ff0…b7c5
0x34b655…2a6f
2 touches
0 conflicts
0x4793c129…1308
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 0xc158f1d988…ebbc17
Audit this contract →
← previous block·next block →recent activity