← previous blocknext block →recent activity
Analyzing
Block #92,275,763
16 transactions · 14 stateful · 2026-08-01 18:37:50 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,275,763 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5490a87…0df8
0x34b655…2a6f
4 touches
1 conflict
0x1e335bfe…ee7f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x2885cd6f…0d9b
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc5490a87bd…4b0df8
Audit this contract →
← previous block·next block →recent activity