← previous blocknext block →recent activity
Analyzing
Block #96,027,629
13 transactions · 12 stateful · 2026-08-14 21:43:42 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,027,629 · 13 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
1w02w13w04w16w18w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd198ef38…4265
0x34b655…2a6f
6 touches
3 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7214
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity