← previous blocknext block →recent activity
Analyzing
Block #94,915,637
18 transactions · 17 stateful · 2026-08-11 00:14:39 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,915,637 · 18 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
1w02w15w26w37w08w19w010w111w414w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a2eb8e…ba35
0x34b655…2a6f
10 touches
10 conflicts
0xa8e98b9f…5935
0x01bff4…1071
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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
10 conflicts on slot 0x70a2eb8e28…92ba35
Audit this contract →
← previous block·next block →recent activity