← previous blocknext block →recent activity
Analyzing
Block #97,853,256
17 transactions · 15 stateful · 2026-08-21 07:48:54 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,853,256 · 17 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
3w04w17w110w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676b5eb4…0b33
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x0353fb4b…6348
0x34b655…2a6f
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x158251ed…ccb3
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
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
3 conflicts on slot 0x676b5eb480…240b33
Audit this contract →
← previous block·next block →recent activity