← previous blocknext block →recent activity
Analyzing
Block #81,627,689
19 transactions · 17 stateful · 2026-06-16 08:56:58 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,627,689 · 19 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
4w09w110w211w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6f117e50…3648
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
6 touches
3 conflicts
0xe59df86b…a00c
0x34b655…2a6f
6 touches
3 conflicts
0xa51de3df…c65a
0x34b655…2a6f
5 touches
3 conflicts
0xc0ee8ce1…0778
0x34b655…2a6f
4 touches
2 conflicts
0x213a54fa…c85f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity