← previous blocknext block →recent activity
Analyzing
Block #80,843,368
57 transactions · 11 stateful · 2026-06-12 17:52:17 UTC
Parallelism
96/100
Blocked
18%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,843,368 · 57 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
3w04w143w045w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c3bd85e…c4d6
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xf490dd39…679f
0x34b655…2a6f
4 touches
1 conflict
0x0f3b22bf…e574
0x34b655…2a6f
3 touches
1 conflict
0xa23619a7…40e4
0x3bd359…433a
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 0x6c3bd85ea9…26c4d6
Audit this contract →
← previous block·next block →recent activity