← previous blocknext block →recent activity
Analyzing
Block #80,226,955
15 transactions · 9 stateful · 2026-06-09 21:21:40 UTC
Parallelism
87/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,226,955 · 15 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
1w02w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6be79ced…ccac
0x34b655…2a6f
4 touches
1 conflict
0x7d2645cd…5d8e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0xb94103ae…7bb9
0x065c9d…c394
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9538
0x188d58…ea8e
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 0x6be79ced61…44ccac
Audit this contract →
← previous block·next block →recent activity