← previous blocknext block →recent activity
Analyzing
Block #80,824,399
21 transactions · 14 stateful · 2026-06-12 15:45:40 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.14
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,824,399 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xff107718…55e9
0x34b655…2a6f
4 touches
1 conflict
0x96d1516a…a76a
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x15bc6576…3a4a
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 0xc0b9bd73c8…277f1c
Audit this contract →
← previous block·next block →recent activity