← previous blocknext block →recent activity
Analyzing
Block #93,923,520
22 transactions · 22 stateful · 2026-08-07 12:47:10 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,923,520 · 22 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
1w02w03w14w25w16w09w111w112w213w314w316w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x917f99a5…7989
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0xbe7c3ccf…80f2
0x34b655…2a6f
4 touches
1 conflict
0x561246cc…31c3
0xa6afd3…d132
4 touches
1 conflict
0x6d1b72ee…6b78
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
3 conflicts on slot 0x917f99a53e…3d7989
Audit this contract →
← previous block·next block →recent activity