← previous blocknext block →recent activity
Analyzing
Block #80,631,275
22 transactions · 12 stateful · 2026-06-11 18:18:01 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,631,275 · 22 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
1w02w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b5eda5…68d3
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0f82dba2…24d6
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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 0x70b5eda505…d468d3
Audit this contract →
← previous block·next block →recent activity