← previous blocknext block →recent activity
Analyzing
Block #80,217,715
28 transactions · 23 stateful · 2026-06-09 20:20:15 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,217,715 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w310w011w113w115w418w421w223w325w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00ddbbf2…4588
0x34b655…2a6f
10 touches
10 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x10536e59…b234
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0x00ddbbf292…ff4588
Audit this contract →
← previous block·next block →recent activity