← previous blocknext block →recent activity
Analyzing
Block #80,102,918
11 transactions · 6 stateful · 2026-06-09 07:35:06 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,102,918 · 11 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
7w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x5d16aea9…b2cf
0x34b655…2a6f
4 touches
1 conflict
0x5cc78005…4877
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
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 0x8fbde2b3d3…899b8f
Audit this contract →
← previous block·next block →recent activity