← previous blocknext block →recent activity
Analyzing
Block #94,233,693
20 transactions · 16 stateful · 2026-08-08 14:51:53 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,233,693 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w29w314w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x94a77fc9…7577
0x34b655…2a6f
6 touches
3 conflicts
0xc6fabe47…654e
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity