← previous blocknext block →recent activity
Analyzing
Block #94,851,188
9 transactions · 8 stateful · 2026-08-10 18:50:32 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,851,188 · 9 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
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e45f694…f713
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0xc1da8f73…484c
0x34b655…2a6f
2 touches
0 conflicts
0xd59b7c91…d1ef
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 0x3e45f694df…0cf713
Audit this contract →
← previous block·next block →recent activity