← previous blocknext block →recent activity
Analyzing
Block #92,343,273
21 transactions · 20 stateful · 2026-08-02 00:17:21 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,343,273 · 21 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
7w08w09w110w111w215w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a9eeb99…9aff
0x7b9256…1fb2
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x7cb7a1c0…c98c
0x7b9256…1fb2
6 touches
3 conflicts
0x7cb7a1c0…c98d
0x7b9256…1fb2
6 touches
3 conflicts
0x7cb7a1c0…c990
0x7b9256…1fb2
6 touches
3 conflicts
0x8a9eeb99…9afe
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity