← previous blocknext block →recent activity
Analyzing
Block #94,719,789
13 transactions · 12 stateful · 2026-08-10 07:48:03 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,719,789 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w28w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0c159059…39b7
0x34b655…2a6f
2 touches
0 conflicts
0x10a0e8ee…ac08
0x34b655…2a6f
2 touches
0 conflicts
0x19fc7aa9…709e
0x34b655…2a6f
2 touches
0 conflicts
0x262ffe69…b552
0x34b655…2a6f
2 touches
0 conflicts
0x41377979…0a18
0x34b655…2a6f
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
6 conflicts on slot 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity