← previous blocknext block →recent activity
Analyzing
Block #80,788,078
19 transactions · 16 stateful · 2026-06-12 11:43:24 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,788,078 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4fa3b95a…880d
0x34b655…2a6f
4 touches
1 conflict
0x5ffe86ec…761d
0x34b655…2a6f
4 touches
1 conflict
0x75755da1…f498
0x34b655…2a6f
4 touches
1 conflict
0x80c34a02…fadc
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity