← previous blocknext block →recent activity
Analyzing
Block #97,395,724
25 transactions · 25 stateful · 2026-08-19 17:08:29 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,395,724 · 25 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
1w02w04w05w17w28w29w310w413w115w016w117w222w023w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6aa736…a698
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xec431e8f…8c4d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xfe2c1082…db16
0x34b655…2a6f
4 touches
1 conflict
0x48acfd83…7ef0
0x40c49f…2af0
4 touches
1 conflict
0xd7a3d42d…e766
0x40c49f…2af0
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 0x6f6aa736ef…34a698
Audit this contract →
← previous block·next block →recent activity