← previous blocknext block →recent activity
Analyzing
Block #92,769,706
19 transactions · 18 stateful · 2026-08-03 12:03:16 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,769,706 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w210w311w412w513w414w515w016w117w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
8 touches
6 conflicts
0x65c9ccee…efc5
0x34b655…2a6f
8 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
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 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity