← previous blocknext block →recent activity
Analyzing
Block #92,768,305
18 transactions · 17 stateful · 2026-08-03 11:56:13 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,768,305 · 18 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
1w02w05w17w28w010w112w313w414w515w616w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc8304415…4f91
0x34b655…2a6f
6 touches
3 conflicts
0x12ef572c…da2d
0x34b655…2a6f
6 touches
3 conflicts
0x68caa37b…c795
0x34b655…2a6f
4 touches
1 conflict
0x743061ce…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0x7b80de04…86d1
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity