← previous blocknext block →recent activity
Analyzing
Block #94,673,862
30 transactions · 21 stateful · 2026-08-10 03:57:03 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,673,862 · 30 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
1w05w18w09w013w114w015w218w119w122w023w224w125w326w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x156552f7…c066
0x34b655…2a6f
8 touches
6 conflicts
0x74f95963…01a2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3ded1b79…27dc
0x065c9d…c394
6 touches
3 conflicts
0xcf49531c…0c81
0x40c49f…2af0
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
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 0x156552f70b…11c066
Audit this contract →
← previous block·next block →recent activity