← previous blocknext block →recent activity
Analyzing
Block #92,404,234
12 transactions · 12 stateful · 2026-08-02 05:23:55 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,404,234 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x267fe70d…159e
0x34b655…2a6f
6 touches
3 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
4 touches
1 conflict
0x243a0147…318e
0x34b655…2a6f
4 touches
1 conflict
0x3093e806…bde2
0x34b655…2a6f
4 touches
1 conflict
0x3e12fd12…8fc5
0x34b655…2a6f
4 touches
1 conflict
0x45cd503b…4d50
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
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
3 conflicts on slot 0x267fe70d55…3a159e
Audit this contract →
← previous block·next block →recent activity