← previous blocknext block →recent activity
Analyzing
Block #82,327,788
18 transactions · 15 stateful · 2026-06-19 14:46:03 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,327,788 · 18 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
1w07w08w110w112w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
6 touches
3 conflicts
0xd06fb4dc…5204
0x34b655…2a6f
6 touches
3 conflicts
0x2a2fcb7f…9ae6
0x34b655…2a6f
4 touches
1 conflict
0x4b268018…02fb
0x34b655…2a6f
4 touches
1 conflict
0x5d32a251…d929
0x34b655…2a6f
4 touches
1 conflict
0x69941f7e…3b1d
0x34b655…2a6f
4 touches
1 conflict
0x6f900be0…cd6e
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
6 conflicts on slot 0x957c875f2a…99b3f9
Audit this contract →
← previous block·next block →recent activity