← previous blocknext block →recent activity
Analyzing
Block #92,761,013
17 transactions · 16 stateful · 2026-08-03 11:19:30 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,761,013 · 17 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
4w05w19w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x5f917ce8…a3c3
0x34b655…2a6f
4 touches
1 conflict
0x87ee379a…cd9e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0xa99b069c…2123
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
1 conflict on slot 0xe8377f798f…125f5e
Audit this contract →
← previous block·next block →recent activity