← previous blocknext block →recent activity
Analyzing
Block #92,330,738
15 transactions · 14 stateful · 2026-08-01 23:14:19 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.93
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,330,738 · 15 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
2w03w04w15w26w27w18w210w011w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc3a300d…617e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x0f94ee4c…1898
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x033cf007…136d
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 0xbc3a300dc5…c0617e
Audit this contract →
← previous block·next block →recent activity