← previous blocknext block →recent activity
Analyzing
Block #80,743,934
11 transactions · 10 stateful · 2026-06-12 06:49:08 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,743,934 · 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
1w04w15w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4badb17…7567
0x065c9d…c394
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x1191e716…b60b
0x065c9d…c394
3 touches
1 conflict
0xd8b5c754…3097
0x065c9d…c394
3 touches
1 conflict
0x40078716…8f30
0x065c9d…c394
3 touches
1 conflict
0x9b00bff4…08b5
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xc4badb175e…c57567
Audit this contract →
← previous block·next block →recent activity