← previous blocknext block →recent activity
Analyzing
Block #92,015,430
18 transactions · 17 stateful · 2026-07-31 20:48:31 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,015,430 · 18 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
1w04w15w06w17w28w212w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x436c4894…08f6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x258fcae9…4c6f
0x7b9256…1fb2
6 touches
3 conflicts
0x258fcae9…4c70
0x7b9256…1fb2
6 touches
3 conflicts
0x258fcae9…4c73
0x7b9256…1fb2
6 touches
3 conflicts
0x2c4c2bef…9a91
0x7b9256…1fb2
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity