← previous blocknext block →recent activity
Analyzing
Block #82,978,413
23 transactions · 19 stateful · 2026-06-22 15:12:55 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,978,413 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w28w09w118w319w020w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf4636f…b2a2
0x34b655…2a6f
6 touches
3 conflicts
0xfdc27a9e…d94d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x36a49c16…89b9
0xc8689a…ee79
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x61e4eb84…0752
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 0xedf4636f60…72b2a2
Audit this contract →
← previous block·next block →recent activity