← previous blocknext block →recent activity
Analyzing
Block #92,187,536
13 transactions · 13 stateful · 2026-08-01 11:14:07 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,187,536 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x39170030…825d
0x065c9d…c394
2 touches
0 conflicts
0x43d2be34…0a81
0x065c9d…c394
2 touches
0 conflicts
0x94f85e71…b59b
0x065c9d…c394
2 touches
0 conflicts
0xdc7aad5c…bce8
0x065c9d…c394
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 0xc1aa38d029…67a9f3
Audit this contract →
← previous block·next block →recent activity