← previous blocknext block →recent activity
Analyzing
Block #94,857,261
13 transactions · 12 stateful · 2026-08-10 19:21:04 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,857,261 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x9e5adfc8…489d
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xfa49615a…b445
0x34b655…2a6f
4 touches
1 conflict
0x401a563c…0ae7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
2 touches
0 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
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity