← previous blocknext block →recent activity
Analyzing
Block #93,487,523
25 transactions · 24 stateful · 2026-08-06 00:14:51 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,487,523 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w08w39w410w511w616w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2741f63d…a456
0x34b655…2a6f
8 touches
6 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
8 touches
6 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0xa3834f05…a4cf
0x34b655…2a6f
6 touches
3 conflicts
0xabf57eb6…416d
0x34b655…2a6f
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 0x2741f63d2b…e2a456
Audit this contract →
← previous block·next block →recent activity