← previous blocknext block →recent activity
Analyzing
Block #92,763,180
19 transactions · 18 stateful · 2026-08-03 11:30:25 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,763,180 · 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
2w04w15w28w39w410w513w616w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6b2ba712…0214
0x34b655…2a6f
6 touches
3 conflicts
0x7ce634d7…d9dd
0x34b655…2a6f
6 touches
3 conflicts
0xe5ef9751…101f
0x34b655…2a6f
6 touches
3 conflicts
0xca2926e0…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x50260e8c…4789
0x34b655…2a6f
4 touches
1 conflict
0x807bf45f…5016
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity