← previous blocknext block →recent activity
Analyzing
Block #82,047,892
19 transactions · 16 stateful · 2026-06-18 07:39:12 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,047,892 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w08w110w014w115w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x8e8f0055…5527
0x34b655…2a6f
6 touches
3 conflicts
0x26abe30c…f680
0x34b655…2a6f
4 touches
1 conflict
0x5af16bfb…038d
0x34b655…2a6f
4 touches
1 conflict
0x5b101190…060e
0x34b655…2a6f
4 touches
1 conflict
0x648518dd…5803
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity