← previous blocknext block →recent activity
Analyzing
Block #92,548,514
16 transactions · 16 stateful · 2026-08-02 17:29:33 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,548,514 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w38w19w411w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaf1352f4…49be
0x34b655…2a6f
8 touches
6 conflicts
0xc9f4535e…4e1d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0xaa179075…fdee
0x34b655…2a6f
6 touches
3 conflicts
0x47ed2719…adc6
0x34b655…2a6f
6 touches
3 conflicts
0xdb5c0730…e75d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity