← previous blocknext block →recent activity
Analyzing
Block #81,876,399
24 transactions · 19 stateful · 2026-06-17 12:34:05 UTC
Parallelism
88/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,876,399 · 24 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
1w03w15w06w17w28w010w111w012w113w214w016w118w220w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x1a623427…24af
0x34b655…2a6f
4 touches
1 conflict
0x51b956b6…1e3f
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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
3 conflicts on slot 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity