← previous blocknext block →recent activity
Analyzing
Block #92,358,244
14 transactions · 12 stateful · 2026-08-02 01:32:38 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,358,244 · 14 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
2w06w08w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68f3fc6b…80ec
0x34b655…2a6f
4 touches
1 conflict
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0x19bbf80f…0615
0x34b655…2a6f
4 touches
1 conflict
0xdadee63d…484c
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xfc4aef18…68fa
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x8b60248a…c7be
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 0x68f3fc6b78…e980ec
Audit this contract →
← previous block·next block →recent activity