← previous blocknext block →recent activity
Analyzing
Block #92,821,322
21 transactions · 20 stateful · 2026-08-03 16:22:57 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,821,322 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w29w010w114w315w416w517w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3542128c…f6c4
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
5 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 0x3542128cd0…2ef6c4
Audit this contract →
← previous block·next block →recent activity