← previous blocknext block →recent activity
Analyzing
Block #83,638,847
20 transactions · 16 stateful · 2026-06-25 16:45:28 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,638,847 · 20 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
2w03w17w08w112w213w214w015w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b1df992…40eb
0x34b655…2a6f
8 touches
6 conflicts
0x049cca71…b102
0x34b655…2a6f
8 touches
6 conflicts
0x8ae827f1…aa36
0x34b655…2a6f
6 touches
3 conflicts
0x177da7f9…4fe4
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x99807814…f8ac
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0x4fbf296b…b9ea
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 0x1b1df992d7…8240eb
Audit this contract →
← previous block·next block →recent activity