← previous blocknext block →recent activity
Analyzing
Block #97,360,414
21 transactions · 15 stateful · 2026-08-19 13:48:51 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,360,414 · 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
1w04w18w09w110w212w315w017w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54be4d07…5249
0x34b655…2a6f
8 touches
6 conflicts
0x4d885229…cc59
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xa3f095f5…bd87
0x34b655…2a6f
4 touches
1 conflict
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x54be4d0749…1a5249
Audit this contract →
← previous block·next block →recent activity