← previous blocknext block →recent activity
Analyzing
Block #79,122,636
13 transactions · 9 stateful · 2026-06-04 18:23:24 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,122,636 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe0a4f97…bc3d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c34
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x62e4b4e7…75a1
0x34b655…2a6f
3 touches
1 conflict
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 conflicts
0xd8fd2add…50fc
0x69df8a…6292
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 0xbe0a4f9745…bebc3d
Audit this contract →
← previous block·next block →recent activity