← previous blocknext block →recent activity
Analyzing
Block #81,479,561
18 transactions · 17 stateful · 2026-06-15 16:30:18 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,479,561 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w17w38w49w510w414w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7a3d42d…e766
0x40c49f…2af0
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x48acfd83…7ef0
0x40c49f…2af0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
6 touches
3 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: 0x40c49f17…d22af0
10 conflicts on slot 0xd7a3d42dc0…66e766
Audit this contract →
← previous block·next block →recent activity