← previous blocknext block →recent activity
Analyzing
Block #92,345,705
12 transactions · 10 stateful · 2026-08-02 00:29:35 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,345,705 · 12 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
2w05w16w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb07f01e3…0ad4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x11376762…a408
0x34b655…2a6f
4 touches
1 conflict
0x1eb410fd…591d
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x4ac2a863…cba1
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 0xb07f01e333…f40ad4
Audit this contract →
← previous block·next block →recent activity