← previous blocknext block →recent activity
Analyzing
Block #97,826,542
21 transactions · 21 stateful · 2026-08-21 05:32:20 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,826,542 · 21 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
2w03w16w07w08w110w211w112w214w316w017w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921893c3…b9b6
0x34b655…2a6f
8 touches
6 conflicts
0x0eccef84…202d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2407edc1…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x2728cd60…78cc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x6e326e1c…482a
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
6 conflicts on slot 0x921893c31c…45b9b6
Audit this contract →
← previous block·next block →recent activity