← previous blocknext block →recent activity
Analyzing
Block #97,725,419
16 transactions · 14 stateful · 2026-08-20 21:01:58 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,725,419 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w310w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91132a87…2232
0x34b655…2a6f
6 touches
3 conflicts
0x157f647d…be9d
0x34b655…2a6f
6 touches
3 conflicts
0x247c79f2…e698
0x34b655…2a6f
4 touches
1 conflict
0x06a27525…f082
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
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 0x91132a87ef…ed2232
Audit this contract →
← previous block·next block →recent activity