← previous blocknext block →recent activity
Analyzing
Block #97,358,882
21 transactions · 21 stateful · 2026-08-19 13:40:57 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,358,882 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w29w310w413w514w417w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3f6f7c8…2436
0x34b655…2a6f
12 touches
15 conflicts
0x0f4f3ced…4674
0x34b655…2a6f
6 touches
3 conflicts
0x255c6128…243f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
15 conflicts on slot 0xa3f6f7c8bd…f22436
Audit this contract →
← previous block·next block →recent activity