← previous blocknext block →recent activity
Analyzing
Block #97,512,188
22 transactions · 20 stateful · 2026-08-20 02:56:29 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,512,188 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w08w09w110w114w218w020w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dcc0868…26bf
0x34b655…2a6f
6 touches
3 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x6235fbc3…aa1e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0x2362c85a…df78
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 0x2dcc08681d…0026bf
Audit this contract →
← previous block·next block →recent activity