← previous blocknext block →recent activity
Analyzing
Block #81,480,427
25 transactions · 24 stateful · 2026-06-15 16:36:05 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,480,427 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w08w110w212w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc740dd24…9801
0x3bd359…433a
6 touches
3 conflicts
0x44ad89ba…cf83
0x5df178…7777
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0001
0x2c492d…444e
6 touches
3 conflicts
0x00000000…0000
0x2c492d…444e
6 touches
3 conflicts
0x73131ffc…b46c
0x5df178…7777
6 touches
3 conflicts
0x90f07a4f…d932
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity