← previous blocknext block →recent activity
Analyzing
Block #82,969,078
19 transactions · 16 stateful · 2026-06-22 14:10:30 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,969,078 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w110w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd45bf713…49a6
0x34b655…2a6f
8 touches
6 conflicts
0x62db95d4…351c
0x34b655…2a6f
7 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
4 touches
1 conflict
0xbd7e0241…07f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5d6dae1…47ff
0x34b655…2a6f
4 touches
1 conflict
0xecebc0df…5495
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
6 conflicts on slot 0xd45bf7138a…3049a6
Audit this contract →
← previous block·next block →recent activity