← previous blocknext block →recent activity
Analyzing
Block #94,812,701
16 transactions · 16 stateful · 2026-08-10 15:36:54 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,812,701 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w410w011w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x02ad5c19…f593
0x34b655…2a6f
4 touches
1 conflict
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x401a563c…0ae7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9fbc6a76…9c29
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
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
21 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity