← previous blocknext block →recent activity
Analyzing
Block #80,272,200
24 transactions · 16 stateful · 2026-06-10 02:23:30 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,272,200 · 24 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
1w03w15w06w27w38w19w215w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xe305e8…e95e
6 touches
3 conflicts
0xde852bc4…30b5
0x7db552…cc3e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb81b3c18…d0be
0x3bd359…433a
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xeeb38aa7…8f00
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0x9e0805ac…1804
0x3bd359…433a
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: 0xe305e87c…57e95e
3 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity