← previous blocknext block →recent activity
Analyzing
Block #97,477,359
23 transactions · 22 stateful · 2026-08-20 00:01:15 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,477,359 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w06w17w08w29w110w111w014w116w117w318w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7bfb5fd…cb38
0x34b655…2a6f
6 touches
3 conflicts
0x609a25a3…8785
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x25d909da…1722
0x34b655…2a6f
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x3315ffd1…722e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xf7bfb5fdd1…6acb38
Audit this contract →
← previous block·next block →recent activity