← previous blocknext block →recent activity
Analyzing
Block #97,900,470
22 transactions · 19 stateful · 2026-08-21 11:51:58 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,900,470 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w08w39w110w312w013w118w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x643e47e3…69f4
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc5dc29f0…f0c6
0x34b655…2a6f
5 touches
3 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
5 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xdf352747…7eaf
0x34b655…2a6f
4 touches
1 conflict
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 0x643e47e358…3d69f4
Audit this contract →
← previous block·next block →recent activity