← previous blocknext block →recent activity
Analyzing
Block #80,743,116
49 transactions · 6 stateful · 2026-06-12 06:43:39 UTC
Parallelism
96/100
Blocked
17%
Avg conflicts / tx
0.02
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,743,116 · 49 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
27w043w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4886c4ce…26e3
0x34b655…2a6f
4 touches
1 conflict
0x92d4e9d1…b273
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xffb8950c…23c6
0x34b655…2a6f
4 touches
1 conflict
0x71829416…4ff2
0x34b655…2a6f
4 touches
1 conflict
0x5babb0df…9cf9
0x34b655…2a6f
2 touches
0 conflicts
0x60ad7285…2ca5
0x34b655…2a6f
2 touches
0 conflicts
0x8d0bf98a…b467
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 0x4886c4ce93…7526e3
Audit this contract →
← previous block·next block →recent activity