← previous blocknext block →recent activity
Analyzing
Block #82,975,890
19 transactions · 16 stateful · 2026-06-22 14:56:04 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,975,890 · 19 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
5w06w17w28w310w011w116w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe732567d…b65d
0x34b655…2a6f
10 touches
10 conflicts
0x7ea6a117…f2f2
0x34b655…2a6f
10 touches
10 conflicts
0x7e17e82a…9748
0x34b655…2a6f
10 touches
10 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
8 touches
6 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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity