← previous blocknext block →recent activity
Analyzing
Block #94,846,730
16 transactions · 15 stateful · 2026-08-10 18:28:06 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,846,730 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w08w39w411w514w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74453e0e…8d7b
0x34b655…2a6f
12 touches
15 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x65f90aa4…c97f
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
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
15 conflicts on slot 0x74453e0e3f…0f8d7b
Audit this contract →
← previous block·next block →recent activity