← previous blocknext block →recent activity
Analyzing
Block #93,347,496
23 transactions · 22 stateful · 2026-08-05 12:30:51 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,347,496 · 23 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
3w04w15w26w37w08w09w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd0e8089…4e3c
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc4f178d6…5153
0x34b655…2a6f
7 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
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 0xcd0e8089bb…aa4e3c
Audit this contract →
← previous block·next block →recent activity