← previous blocknext block →recent activity
Analyzing
Block #92,515,951
19 transactions · 17 stateful · 2026-08-02 14:45:48 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,515,951 · 19 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
2w04w15w06w07w18w213w014w115w216w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc2c6a3a8…5998
0x34b655…2a6f
6 touches
3 conflicts
0x0359c13d…9da4
0x34b655…2a6f
6 touches
3 conflicts
0x4fb86cd0…c67c
0x34b655…2a6f
4 touches
1 conflict
0x5649379f…d9eb
0x34b655…2a6f
4 touches
1 conflict
0x640fd1c6…d624
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity