← previous blocknext block →recent activity
Analyzing
Block #94,316,239
18 transactions · 15 stateful · 2026-08-08 21:50:11 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,316,239 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f28eb14…e5ef
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x08b68583…01a1
0x34b655…2a6f
2 touches
0 conflicts
0x14b29ddb…0fd3
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
2 touches
0 conflicts
0x38855b14…b4ec
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
1 conflict on slot 0x6f28eb14f4…68e5ef
Audit this contract →
← previous block·next block →recent activity